Skip to content

ASDF/DEFSYSTEM in automatically generated .asd files #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
avodonosov opened this issue Oct 21, 2013 · 4 comments
Closed

ASDF/DEFSYSTEM in automatically generated .asd files #2

avodonosov opened this issue Oct 21, 2013 · 4 comments

Comments

@avodonosov
Copy link

Hello.

When someone generates .asd file programatically,
and uses some new version of ASDF, the DEFSYSTEM
symbol is printed as ASDF/DEFSYSTEM:DEFSYSTEM
instead of just ASDF:DEFSYSTEM.

This is because in the newer versions ASDF
package is an umbrella package reexporting
symbols from subcomponent packages like
ASDF/DEFSYSTEM.

The .asd files generated that way do not work
on older versions of ASDF (shipped with CCL 1.8,
sbcl-1.1, ecl-12.12.1 and other lisps).

Quicklisp automatically generates .asd files
for several projects distributed as a single .lisp file.
For example string-case, macroexpand-dammit, memoize.

In result such single-file projects which were updated in
Quicklisp 2013-10-03 are broken on old lisps:
http://common-lisp.net/project/cl-test-grid/ql/quicklisp-2013-10-03-diff2.html

@quicklisp
Copy link
Owner

Thanks. Pascal Costanza also noticed this and I will fix it and make a new release.

@quicklisp
Copy link
Owner

de79404 fixes this problem, and the new release will have updated system files with compatible symbols in them.

@vigneshsarma
Copy link

This doesn't seem available yet?
Does this take some time?

CL-USER> (ql:update-all-dists)
1 dist to check.
You already have the latest version of "quicklisp": 2013-10-03.
NIL
CL-USER> (ql:update-client)
Installed version 2012112500 is as new as upstream version 2012112500. No update.
T

@quicklisp
Copy link
Owner

It will not be available until the next dist update, which I will
announce on blog.quicklisp.org. I hope to make the update available in
the next few days.

Zach

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants