Lisp HUG Maillist Archive

quicklisp/quicklisp.lisp and *default-pathname-defaults*

Unable to parse email body. Email id is 11734

Re: quicklisp/quicklisp.lisp and *default-pathname-defaults*

On Wednesday, August 22, 2012 at 7:31 AM, Nick Levine wrote:
Is LW at fault? Is Quicklisp at fault? Am I? Or is it the CL
specification?

Would anyone like to venture any opinions?
 
I'll go with 6) All of the above.

Keith M Corbett


Re: quicklisp/quicklisp.lisp and *default-pathname-defaults*


* Nick Levine <201208221131.q7MBVH3N041532@raven.ravenbrook.com> :
Wrote on Wed, 22 Aug 2012 12:31:17 +0100 (BST):

| As its final act the Quicklisp installer (quicklisp.lisp from
| http://beta.quicklisp.org/) sets *default-pathname-defaults*:
|
|;;; Try to canonicalize to an absolute pathname; helps on Lisps where
|;;; *default-pathname-defaults* isn't an absolute pathname at startup
|;;; (e.g. CCL, CMUCL)
|(setf *default-pathname-defaults* (truename *default-pathname-defaults*))
| Would anyone like to venture any opinions?

The only sensible value for *d-p-d* is #p"".  Any program that tries to
change this is not a general purpose program, but is malicious: and you
can consider your environment to be contaminated and you are not
programming in common lisp anymore, but for someone's specific
"distribution platform".

If you are using quicklisp, you may already have lost.

On those lines, I would suggest that LW remove asdf from their packaging
and not ship it out of the box.  If users want to shoot themselves in the
foot, let them download it from the vendor of asdf

--- Madhu

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html


Updated at: 2020-12-10 08:36 UTC