Well, one reason uiop.asd is one level down is to make it easier to package uiop separately for use by e.g. quicklisp. One reason asdf.asd isn't down in a subdirectory called defsystem/ is that asdf.lisp is in build/
Neither of these reasons is unsurmountable. But at this point, I don't see much value in fighting them.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org An extreme optimist is a man who believes that humanity will probably survive even if it doesn't take his advice. — John McCarthy
On Tue, Apr 16, 2013 at 6:01 PM, Robert Goldman rpgoldman@sift.info wrote:
I was wondering if it would be possible to bump the uiop.asd file up to be a sibling of asdf.asd.
It seems odd to me that asdf.asd is at the top level, and has build/asdf.lisp under it, but that uiop.asd is in uiop/.
Odd + it means I need now to do
(push "home:lisp;asdf;" asdf:*central-registry*) and (push "home:lisp;asdf;uiop;" asdf:*central-registry*)
to upgrade....
Any reason why uiop.asd couldn't be at the top level?
thanks, r