From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Another load path idea
Date: Sat, 07 Jan 2006 13:42:47 +0000 [thread overview]
Message-ID: <877j9cnoh4.fsf@ossau.uklinux.net> (raw)
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
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2006-01-07 13:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 13:42 Neil Jerram [this message]
2006-01-12 9:38 ` Another load path idea Ludovic Courtès
2006-01-12 17:44 ` Neil Jerram
2006-01-19 9:21 ` Ludovic Courtès
2006-01-20 21:21 ` Kevin Ryde
2006-01-21 9:01 ` Neil Jerram
2006-01-22 15:38 ` Andy Wingo
2006-01-26 0:55 ` Kevin Ryde
2006-01-26 8:39 ` Ludovic Courtès
2006-01-26 20:19 ` Neil Jerram
2006-01-26 23:00 ` Kevin Ryde
2006-01-27 8:57 ` Ludovic Courtès
2006-01-28 0:39 ` Kevin Ryde
2006-01-30 9:11 ` Ludovic Courtès
2006-02-04 16:44 ` Neil Jerram
2006-01-29 22:39 ` Greg Troxel
2006-01-31 20:23 ` Kevin Ryde
2006-01-31 20:58 ` Greg Troxel
2006-01-23 8:27 ` Ludovic Courtès
2006-01-23 20:04 ` Neil Jerram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877j9cnoh4.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).