From: Rob Browning <rlb@defaultvalue.org>
Cc: Marius Vollmer <marius.vollmer@uni-dortmund.de>,
guile-devel <guile-devel@gnu.org>, Greg Troxel <gdt@ir.bbn.com>
Subject: Re: The load path
Date: Sat, 06 Nov 2004 15:21:52 -0600 [thread overview]
Message-ID: <87wtwyk70v.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <418D0EAE.40703@ossau.uklinux.net> (Neil Jerram's message of "Sat, 06 Nov 2004 17:49:34 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
> Yes, I understood that; I'm currently inclined against the proposal.
See my recent reply to Paul. After some thinking, I'm similarly
inclined.
> - The set of %load-path directories is a distribution decision, not
> a per-package decision. In general, I think applications should be
> strongly encouraged to install their Scheme code in one of the
> distribution-wide %load-path locations, not in some
> application-specific directory (which would then need to be added to
> %load-path).
Agreed, with the one caveat that until/unless we end up with some
better module versioning support, we may need a bit of policy, at
least within distributions that support multiple installed versions of
Guile.
Imagine there's a guile add-on module package foo. Also imagine that
it works fine with guile-1.6 and guile-1.8, but not guile-2.0. It
needs to be able to arrange for itself to be available via
(use-modules (foo)) in the first two cases, but not in the last.
One easy way to do that with the current system would be to just tell
the add-on packages to put their files elsewhere (say /usr/share/foo)
and then set up the right symlinks during installation:
/usr/share/guile/1.6/foo -> ../../foo
/usr/share/guile/1.8/foo -> ../../foo
Of course Guile still needs better support for multiple installed
versions, presuming we're interested in such support upstream (bin/*
in particular). Otherwise, I can continue to just work on that in
Debian.
> In my view, relying on the ordering of load path components is the
> way of madness (except in the particular-user-experimenting mode,
> where a user prepends their own directory to the load path in order
> to experiment), and it would be far better to agree guidelines for
> unique module names, and to work out a solution for module
> versioning.
I agree completely.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-11-06 21:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-16 17:52 The load path Andy Wingo
2004-10-17 19:40 ` Rob Browning
2004-10-17 23:13 ` Greg Troxel
2004-11-05 15:05 ` Marius Vollmer
2004-11-05 15:25 ` Paul Jarc
2004-11-05 16:43 ` Rob Browning
2004-11-05 17:43 ` Paul Jarc
2004-11-05 18:59 ` Rob Browning
2004-11-05 19:22 ` Paul Jarc
2004-11-05 22:05 ` Rob Browning
2004-11-06 7:25 ` Paul Jarc
2004-11-06 16:19 ` Rob Browning
2004-11-06 22:58 ` Rob Browning
2004-11-05 16:15 ` Rob Browning
2004-11-05 17:31 ` Andreas Rottmann
2004-11-05 18:57 ` Greg Troxel
2004-11-05 19:07 ` Rob Browning
2004-11-05 19:19 ` Greg Troxel
2004-11-05 23:53 ` Neil Jerram
2004-11-06 4:54 ` Rob Browning
2004-11-06 14:38 ` Andreas Vögele
2004-11-06 17:49 ` Neil Jerram
2004-11-06 21:21 ` Rob Browning [this message]
2004-11-07 18:46 ` Neil Jerram
2004-11-07 21:16 ` Rob Browning
2004-11-09 15:22 ` Paul Jarc
2004-11-10 18:43 ` Andy Wingo
2004-11-11 13:23 ` Greg Troxel
2004-11-12 21:31 ` Neil Jerram
2004-11-13 0:22 ` Greg Troxel
2004-11-13 1:08 ` Rob Browning
2004-11-13 16:12 ` Greg Troxel
2004-11-14 11:02 ` Neil Jerram
2004-11-14 14:05 ` Greg Troxel
2004-11-18 19:44 ` Neil Jerram
2004-11-19 14:46 ` Greg Troxel
2004-11-14 10:48 ` Neil Jerram
2004-11-15 16:43 ` Andy Wingo
2004-11-18 19:54 ` 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=87wtwyk70v.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=marius.vollmer@uni-dortmund.de \
/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).