Solved (was: Re: [asdf-devel] (asdf:system-source-directory :uiop) not working after upgrade to 3.0.2.25)

2013-10-22 Thread Dave Cooper
It's not crucial that I release with this latest 3.0.2.32, but I just bring up this issue in case it is actually a lurking asdf bug which needs to be shaken out before 3.0.3 release... If something is broken, we definitely want to solve before release. But I fear the problem is with

Re: Solved (was: Re: [asdf-devel] (asdf:system-source-directory :uiop) not working after upgrade to 3.0.2.25)

2013-10-22 Thread Faré
On Tue, Oct 22, 2013 at 2:08 PM, Dave Cooper david.coo...@genworks.com wrote: I solved the issue by the following bootstrap procedure: 1. compile/load adsf3 2. (remhash uiop asdf::*preloaded-systems* 3. load quicklisp's setup.lisp Without step (2), the preloaded system of uiop occurs first

Re: Solved (was: Re: [asdf-devel] (asdf:system-source-directory :uiop) not working after upgrade to 3.0.2.25)

2013-10-22 Thread Dave Cooper
On Tue, Oct 22, 2013 at 3:27 PM, Faré fah...@gmail.com wrote: I suppose the solution is for search-for-system-definition to treat sysdef-preloaded-system-search specially and put it at the end of the search, just like it magically puts find-system-if-being-defined first. For backward

[asdf-devel] Re: Solved

2013-10-22 Thread Faré
On Tue, Oct 22, 2013 at 3:55 PM, Zach Beane x...@xach.com wrote: Faré fah...@gmail.com writes: I suppose the solution is for search-for-system-definition to treat sysdef-preloaded-system-search specially and put it at the end of the search, just like it magically puts

Re: Solved (was: Re: [asdf-devel] (asdf:system-source-directory :uiop) not working after upgrade to 3.0.2.25)

2013-10-22 Thread Faré
—♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org On Tue, Oct 22, 2013 at 3:57 PM, Dave Cooper david.coo...@genworks.com wrote: I suppose the solution is for search-for-system-definition to treat sysdef-preloaded-system-search specially and put it at the end of the

[asdf-devel] Re: Solved

2013-10-22 Thread Zach Beane
Faré fah...@gmail.com writes: No, that's the opposite: if it's preloaded, it should *never* be found in preference to anything else, it's just available in the image as a fallback in case no source code was found. And I don't want people to have to retroactively modify quicklisp so it bumps

[asdf-devel] Re: Solved

2013-10-22 Thread Faré
On Tue, Oct 22, 2013 at 4:36 PM, Zach Beane x...@xach.com wrote: Faré fah...@gmail.com writes: preloaded means: the code is already in the image, though the source might not be available. Thanks for clarifying. Can this behavior only be changed by modifying the internals of ASDF? I'm not

[asdf-devel] Re: Solved

2013-10-22 Thread Zach Beane
Faré fah...@gmail.com writes: I'm not sure what you call this behavior, but yes, upgrade to a new ASDF (and getting it fixed if there's a bug) is probably the official solution as long as ASDF is being maintained. In case ASDF falls back into not being actively maintained anymore, you can