[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Another load path idea

From: Neil Jerram
Subject: Another load path idea
Date: Sat, 07 Jan 2006 13:42:47 +0000
User-agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux)

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?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]