From: Bruce Korb <bkorb@gnu.org>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: "Mark H Weaver" <mhw@netris.org>,
"Ludovic Courtès" <ludo@gnu.org>,
guile-devel <guile-devel@gnu.org>
Subject: Re: Adding to the end of the load path
Date: Fri, 16 Nov 2012 10:06:55 -0800 [thread overview]
Message-ID: <50A680BF.5030208@gnu.org> (raw)
In-Reply-To: <CA+U71=NhCduytPC6E-K8gHHu21BPMrAEhtD70=s0+uH8q7Uqog@mail.gmail.com>
On 11/15/12 16:10, Noah Lavine wrote:
> Given that the module-lookup system is fundamentally complicated, I'm going to
> suggest that we *don't* try to make it all configurable by environment variables.
> If people want full control of lookups, they can write a site-wide Guile init
> file or a personal ~/.guile. The regular load-path would still be part of the
> system, and that would be configurable by an environment variable, so legacy
> setups would continue to work. However, I'd be happy saying that if you wanted
> to access all of the functionality, you need to write Scheme code. Let's start
> by adding Scheme interfaces to the functionality we want, and maybe not worry
> about environment variables if they're complicated.
>
> What do you think?
Yes!! With that, can the LD_LIBRARY_PATH be freed from fiddling?
next prev parent reply other threads:[~2012-11-16 18:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 3:18 Adding to the end of the load path Ian Price
2012-11-08 1:03 ` Andreas Rottmann
2012-11-11 7:50 ` Mark H Weaver
2012-11-11 19:02 ` Andreas Rottmann
2012-11-11 21:51 ` Mark H Weaver
2012-11-12 16:35 ` Bruce Korb
2012-11-13 21:04 ` Ludovic Courtès
2012-11-15 22:06 ` Andreas Rottmann
2012-11-15 22:37 ` Ludovic Courtès
2012-11-15 22:44 ` Mark H Weaver
2012-11-15 23:06 ` Ludovic Courtès
2012-11-16 0:10 ` Noah Lavine
2012-11-16 14:00 ` Noah Lavine
2012-11-16 18:06 ` Bruce Korb [this message]
2012-11-16 18:52 ` Mark H Weaver
2012-11-16 21:38 ` Noah Lavine
2012-11-28 23:12 ` [PATCH] Add parse-path-with-ellipsis, and use it for GUILE_LOAD_PATH et al Mark H Weaver
2012-11-28 23:46 ` Ludovic Courtès
2012-11-29 3:04 ` Mark H Weaver
2012-11-29 10:27 ` Ludovic Courtès
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=50A680BF.5030208@gnu.org \
--to=bkorb@gnu.org \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mhw@netris.org \
--cc=noah.b.lavine@gmail.com \
/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).