From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: Guile Users <guile-user@gnu.org>
Subject: Re: Another load path idea
Date: Thu, 12 Jan 2006 10:38:42 +0100 [thread overview]
Message-ID: <87oe2hss4d.fsf@laas.fr> (raw)
In-Reply-To: <877j9cnoh4.fsf@ossau.uklinux.net> (Neil Jerram's message of "Sat, 07 Jan 2006 13:42:47 +0000")
Hi,
Neil Jerram <neil@ossau.uklinux.net> writes:
> 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?
Yes, but I think that's (almost) a different issue. I think it solves
the issue of finding the right dependency, not that of finding the right
module. IOW, it's similar to Libtool's `.la' files (which include
information about a library's dependencies), not to /etc/ld.so.conf .
Speaking of that, the analogy of `ld.so.conf' would be something along
the lines of what you originally proposed[0]: storing the initial value
of `%load-path' somewhere in a file (or bunch of file -- the `init.d'
approach[1]), instead of having it hard-wired.
The `init.d' approach was ruled out because of the increased startup
time[2]. However, the single file approach had been considered
unpractical because it is harder to add/remove directories from there,
and to keep track of which packages exactly relied on it[1].
So, what if we just went ahead with the `init.d' approach, except that
each file would only contain a single Scheme string? This constraint is
critical to address the startup time concern.
Or what about a single init file (again without any code, only data),
somewhat enhanced to keep track of which package rely on a each
particular load path:
((guile-gnome . "/opt/guile-gnome/")
(guile-chbouib . "/usr/local/share/guile-chbouib")
... )
I'm sorry for getting back to this kind of proposal, but I think I'm
getting confused. Since the discussion spanned over several months,
summarizing the key arguments seems important at this point.
Thanks,
Ludovic.
[0] http://lists.gnu.org/archive/html/guile-user/2005-10/msg00036.html
[1] http://lists.gnu.org/archive/html/guile-user/2005-10/msg00109.html
[2] http://lists.gnu.org/archive/html/guile-user/2005-12/msg00000.html
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-01-12 9:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 13:42 Another load path idea Neil Jerram
2006-01-12 9:38 ` Ludovic Courtès [this message]
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=87oe2hss4d.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
--cc=guile-user@gnu.org \
/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).