There has not been a resounding consensus for any of the proposals
discussed so far, so here is another possibility.
The basic idea behind all of the previous proposals was to create some
kind of config when a package was installed, such that other Guile
code would be able to find that package automatically. But what if we
do things the other way round? When a package that has dependencies
on other Guile modules is installed, we do some work at install time
to locate the dependencies that the package needs, and save the
results in a config file under the name of the _using_ package. Then
when that package is run, it sets up the environment that it needs by
reading the saved config file.
I have no idea how to do this yet, but is it a good idea in principle?
Regards,
Neil
_______________________________________________
Guile-user mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/guile-user
