[clbuild-devel] [Fwd: Re: [elephant-devel] Problems with elephant on sbcl using postmodern]

[David Lichteblau]

Quoting Leslie P. Polzer (sky at viridian-project.de):
> > That's why it's listed as a "work-needing or prospective project" as
> > opposed to a "main project".  That's our warning sign.
> 
> Sorry for pestering around, but how about giving a bit more
> specific hints as to the pitfall?
> 
> Like "CFFI DOESN'T WORK, YOU NEED UFFI!"? :)

I agree that the whole wnpp distinction is probably not clear enough to
users and would consider accepting a patch that refuses to download
-any- wnpp project without interactive confirmation by the user.  ("You
are about to download a WNPP project.  For details, see if there are
comments in the wnpp-projects file for this project.  If you know what
you're doing, type 'yes'".)

This would have to be overridable in clbuild.conf.

"CFFI DOESN'T WORK, YOU NEED UFFI!" could then go into wnpp-projects an
a comment.

I'm not too fond of the idea of displaying such comments automatically,
because it kind of implies that sb-alien use in elephant is the only
issue that we have with it in clbuild.  Which may or may not be the
case.  But if any clbuild maintainer had the time to say for sure, it
probably wouldn't be a wnpp project in the first place.  Also, such
comments tend to be out of date quickly, and are more harmful than
helpful then.


d.