On Fri, Jan 8, 2010 at 1:29 PM, Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote: > Ouch, we weren't aware of all these issues when we approved common-lisp- > controller in FESCo. :-( It was "sold" to us as something great and working > perfectly. I wasn't aware that it didn't actually work at all at this time > and I strongly doubt the rest of FESCo was either. It makes no sense to have > a packaging guideline mandate using something which doesn't work. The alternative to common-lisp-controller, for libraries at least, is to have lots of subpackages: trivial-features-ccl trivial-features-clisp trivial-features-cmu trivial-features-ecl trivial-features-gcl trivial-features-sbcl And you also have to keep trivial-features-src around in case someone buys an Allegro license. I can see why Debian went with common-lisp-controller for that case. It helps keep insanity at bay. But I think we need to have an escape clause for applications, and also for libraries that take a significant amount of time/space to compile. If we're going to use it for (some) libraries, then we also need to fix it so that it works on as many CLs as possible. A number greater than zero would be good. :-) Some kind of response to the fix I suggested for SBCL in https://bugzilla.redhat.com/show_bug.cgi?id=499182 would be nice, too. I guess I should make that an actual patch instead of a suggested sed operation. :-) Hmmmm, I just looked upstream to see if this has been fixed, and found that the last CVS checkin was 4 years ago. That isn't encouraging. Is upstream dead, or could it be awakened if shouted at? -- Jerry James http://www.jamezone.org/ -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
