[ Sorry for the exploding cc: list - this is a Debian packaging issue, so please limit the follow-ups to debian-devel. ] Mark Galassi <rosalia@cygnus.com> writes: > Jim> Perhaps I should declare a dependency on the slib package, > > Absolutely not! It would be a great loss if Guile were *forced* to > depend on slib. > > Guile is an embeddable library implementing R4RS Scheme, and is quite > useful as that, even without slib. > > That's why I suggested that both Guile and slib try to create the > catalog, that way the one that is installed last will do the creating. > > [by the way, I think that creating the catalog at run time instead of > install time is really non-robust, but we are stuck with what Aubrey > gives us in his otherwise awesome slib] OK. I agree that declaring a dependency isn't really good. I was just being lazy, hoping nobody would call me on it. The code for 'registering' slib with guile ought to be in the slib package (I'm not the maintainer of that package, Rob Browning is). It might go into a 'slibconfig' script. Of course, there are quite a few different Scheme packages other than guile that might also work with slib - so that makes things a bit ugly for Rob. When guile (or another Scheme) is installed on a system that also has slib, it could call the proposed 'slibconfig' script from the slib package. Here's a possible slibconfig script with support for Guile in it: #! /bin/sh if [ -d /usr/share/guile ]; then (cd /usr/share/guile guile -c "(use-modules (ice-9 slib)) (require 'new-catalog)" ) fi This would be called from the postinst of slib and guile. Rob, if you think this is a good idea, I could make a non-maintainer release of slib (only supporting guile) -- or I could wait for you to make a release. Cheers, - Jim
Attachment:
pgpz8G6e6J8ZE.pgp
Description: PGP signature