[clbuild-devel] [PATCH] Broken dependencies, new WNPPs

David Lichteblau david at lichteblau.com
Tue Feb 5 14:22:31 UTC 2008


Hi,

(I'm Cc'ing my reply to clbuild-devel.  I hope that is okay with you.)

Quoting Victor Kryukov (victor.kryukov at gmail.com):
> 1/ Some more packages for your consideration - I believe they should
> go into projects. metabang-bind is the main package here - it provides
> nice "bind" facility, everything else is supporting packages. I've
> included asdf even though it ships with sbcl because the default ASDF
> that ships with sbcl is 10 months old and lacks some useful features -
> I've reported it to sbcl-devel and they will be probably fix it soon.
> 
> metabang-bind    get_darcs http://common-lisp.net/project/metabang-bind
> lift             get_darcs http://common-lisp.net/project/lift/darcs/lift
> asdf-system-connections get_darcs
> http://common-lisp.net/project/cl-containers/asdf-system-connections/darcs/asdf-system-connections
> asdf             get_cvs_full
> :pserver:anonymous at cclan.cvs.sourceforge.net:/cvsroot/cclan asdf

I'm really not comfortable with asdf-system-connections.

For one thing, I'm not familiar enough with it to decide whether it's
good enough for the main projects list or only for wnpp-projects.

In addition, since asdf-system-connections actually defines things
inside the ASDF package, I'm not even sure keeping it in wnpp-projects
would lessen its impact on the rest of clbuild.  Hearing that it might
be incompatible with ASDF as included in SBCL does not lessen my worries
either.

Of course, we would like to support as many Lisp projects as possible,
but being an alternative to a public wiki edited by random people, we
also want to provide just a little bit of quality assurance.

That doesn't mean that clbuild will never support asdf extensions.  But
if such a project is added to clbuild, it needs the support of someone
who is (a) familiar with clbuild and (b) familiar with the project in
question.

If that means we can't add most of Gary King's projects, that's a pity.
But perhaps it also highlights an architectural issue with those
projects and their dependencies.


d.



More information about the clbuild-devel mailing list