Neil Jerram <[EMAIL PROTECTED]> writes: > > In the init.d approach, there would be a directory named > $sysconfdir/guile/X.Y/init.d, and we would distribute an init.scm file > (which Guile normally loads on startup) which would load all the files > in $sysconfdir/guile/X.Y/init.d. So, for example, when a package > guile-foo is installed under $prefix, it would create the file > $sysconfdir/guile/X.Y/init.d/guile-foo with contents: > > (require-load-path-directory "$prefix/wherever/my/scheme/files/are")
What advantage is this over putting a symlink in /usr/share/guile/site to point to this alternate location? What is the wherever/my/scheme/files/are directory likely to be? Guile library packages wouldn't be sprayed randomly across all four corners of the disk would they? _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://lists.gnu.org/mailman/listinfo/guile-user
