[asdf-devel] Fwd: Re: [Openmcl-devel] asdf 2 imported into trunk
This was in the openmcl-devel list. Question: should we bundle a version of ASDF-INSTALL that's known to be compatible? Is there someone we should be talking to who maintains ASDF-INSTALL? cheers, r -------- Original Message -------- Subject: Re: [Openmcl-devel] asdf 2 imported into trunk Date: Fri, 07 May 2010 17:27:53 -0400 From: Raffael Cavallaro <raffaelcavallaro@mac.com> To: openmcl-devel <openmcl-devel@clozure.com> On May 5, 2010, at 10:53 PM, R. Matthew Emerson wrote:
I just updated the trunk's bundled ASDF from upstream.
http://common-lisp.net/project/asdf/
The ASDF maintainers consider this version of ASDF to be a release candidate.
http://common-lisp.net/project/asdf/asdf/FAQ.html includes an entry describing what has changed since ASDF 1.
One notable pitfall: ASDF 2 is not compatible with asdf-binary-locations. ASDF 2 now includes similar functionality itself. Please read the FAQ link above for more information.
Please test it out on your systems. If you find a bug, please report it at https://launchpad.net/asdf or use the asdf mailing list: http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
FWIW, I ran into an issue with the new version of asdf (i.e., asdf 2) and the latest asdf-install. There's a simple, one line fix to the most recent asdf-install to make it work with the asdf 2. In the file installer.lisp which is part of asdf-install, an around method for the generic function find-component has an incompatible lambda list. The latest version of installer.lisp from asdf-install has this: (defmethod asdf:find-component :around ((module (eql nil)) name &optional version) (declare (ignore version)) ... just remove the &optional parameter and the subsequent declaration: (defmethod asdf:find-component :around ((module (eql nil)) name) ... and now asdf-install will load and work properly. (well, it still doesn't pass its own test suite because it tries to use an illegal character in a filename when writing its report, but it does successfully install asdf-installable systems). warmest regards, Ralph Raffael Cavallaro raffaelcavallaro@me.com _______________________________________________ Openmcl-devel mailing list Openmcl-devel@clozure.com http://clozure.com/mailman/listinfo/openmcl-devel
I don't know the status of ASDF-INSTALL. It looks like ASDF-INSTALL is being maintained outside ASDF. We probably should remove the asdf-install and cclan files from our repository. Since ASDF-INSTALL has its own repository, they should probably #+asdf2 ify any compatibility changes. Sorry about that. What other programs use deep ASDF internals and should be checked for breakage? [ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ] To say that power is corrupted is like saying that water is wet. On 7 May 2010 17:37, Robert Goldman <rpgoldman@sift.info> wrote:
This was in the openmcl-devel list.
Question: should we bundle a version of ASDF-INSTALL that's known to be compatible? Is there someone we should be talking to who maintains ASDF-INSTALL?
cheers, r
-------- Original Message -------- Subject: Re: [Openmcl-devel] asdf 2 imported into trunk Date: Fri, 07 May 2010 17:27:53 -0400 From: Raffael Cavallaro <raffaelcavallaro@mac.com> To: openmcl-devel <openmcl-devel@clozure.com>
On May 5, 2010, at 10:53 PM, R. Matthew Emerson wrote:
I just updated the trunk's bundled ASDF from upstream.
http://common-lisp.net/project/asdf/
The ASDF maintainers consider this version of ASDF to be a release candidate.
http://common-lisp.net/project/asdf/asdf/FAQ.html includes an entry describing what has changed since ASDF 1.
One notable pitfall: ASDF 2 is not compatible with asdf-binary-locations. ASDF 2 now includes similar functionality itself. Please read the FAQ link above for more information.
Please test it out on your systems. If you find a bug, please report it at https://launchpad.net/asdf or use the asdf mailing list: http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
FWIW, I ran into an issue with the new version of asdf (i.e., asdf 2) and the latest asdf-install. There's a simple, one line fix to the most recent asdf-install to make it work with the asdf 2.
In the file installer.lisp which is part of asdf-install, an around method for the generic function find-component has an incompatible lambda list. The latest version of installer.lisp from asdf-install has this:
(defmethod asdf:find-component :around ((module (eql nil)) name &optional version) (declare (ignore version)) ...
just remove the &optional parameter and the subsequent declaration:
(defmethod asdf:find-component :around ((module (eql nil)) name) ...
and now asdf-install will load and work properly. (well, it still doesn't pass its own test suite because it tries to use an illegal character in a filename when writing its report, but it does successfully install asdf-installable systems).
warmest regards,
Ralph
Raffael Cavallaro raffaelcavallaro@me.com
_______________________________________________ Openmcl-devel mailing list Openmcl-devel@clozure.com http://clozure.com/mailman/listinfo/openmcl-devel
_______________________________________________ asdf-devel mailing list asdf-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/asdf-devel
On 5/8/10 1:05 AM, Faré wrote:
I don't know the status of ASDF-INSTALL.
It looks like ASDF-INSTALL is being maintained outside ASDF.
We probably should remove the asdf-install and cclan files from our repository.
Since ASDF-INSTALL has its own repository, they should probably #+asdf2 ify any compatibility changes. Sorry about that.
I'm not so sure that ASDF-INSTALL is actively maintained, as the last ChangeLog darcs entry is from 2008. When I went looking to incorporate ASDF-INSTALL into ABCL several months ago, I found a wide divergence of its implementation among the contemporary active Lisp implementations, from which I cherry-picked to get the [version in ABCL][1] [1]: http://trac.common-lisp.net/armedbear/changeset/12487 Wouldn't it make sense for ASDF to subsume the installation code part of ASDF-INSTALL like it subsumed ASDF-BINARY-LOCATIONS? This is certainly a post ASDF2 release question, so it is probably a good idea to remove the files from the ASDF tree as you suggest. It certainly is a vote of confidence in the fidelity of ASDF2's backwards compatibility that ASDF-INSTALL only requires a [minor adjustment][2] to work! [2]: http://trac.common-lisp.net/armedbear/changeset/12657 -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
participants (3)
-
Faré -
Mark Evenson -
Robert Goldman