> 
> > 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 your configuration somehow.
> 


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 in *system-definition-search-functions*, so the separable project for uiop (in my case, in local-projects), never ends up being found, and therefore ends up missing from the monofasl (I do suspect that the fact that it silently fails to be included in the monofasl can be considered a bug -- this probably should throw an error when trying to build the monofasl and realizing that the uiop.fasl is not showing up to the party, shouldn't it?)

So is this a use case which should be more directly supported? Does this call for an unregister-preloaded-system or some such thing? 


Regards,

 Dave



On Tue, Oct 22, 2013 at 10:57 AM, Faré <fahree@gmail.com> wrote:
> So I went ahead and tried
>
>   (load (compile-file "quicklisp/asdf.lisp"))
>
> before loading quicklisp/setup.lisp.
>
If you already changed the quicklisp copy and *required-asdf-version*
to something later than your implementation-provided ones, as I
believe you are, this step is redundant.

> And yes, I copied version.lisp.expr into quicklisp/local-projects/uiop/.
>
Did you use cp -aL with -L to dereference the symlink?
It worked for me.

> To test that it wasn't ignoring the uiop in local-projects because it is the
> same version as what is already loaded, I even temporarily bumped the
> version number in that version.lisp-expr to 3.0.2.33.
>
No, I don't think it's magically checking the version against
downgrade, as it is doing for asdf itself. Maybe it should?

CL_SOURCE_REGISTRY=~/cl/poiu rlwrap sbcl --eval "'(#.(map () 'require
'(:asdf :poiu)) #.(in-package :asdf) #.(load \"~/quicklisp/setup\"))"
* (system-source-directory :uiop)
#P"/home/tunes/quicklisp/local-projects/uiop/"

I didn't even have to (ql:register-local-projects) in that session —
or maybe its effects were persistent across section? Looking at the
source, it builds an index, so you need to run it once after you
installed the copy of uiop, and thereafter its effects should persist.

> Still no dice -- I still get
>
>  (asdf:system-source-directory :uiop)   --> nil
>
> after loading the quicklisp/setup.lisp and (ql:register-local-projects)
>
> Quicklisp works in general after the upgrade. It just can't find the source
> directory (or any source directory) for :uiop.
>

> 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 your configuration somehow.

—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
What one person receives without working for, another person must work for
without receiving. — Adrian Rogers



--
My Best,

Dave Cooper, Genworks Support
david.cooper@genworks.com, dave.genworks.com(skype)
USA: 248-327-3253(o), 1-248-330-2979(mobile)
UK: 0191 645 1699