From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: The load path
Date: Thu, 18 Nov 2004 19:54:56 +0000 [thread overview]
Message-ID: <419CFE10.7090407@ossau.uklinux.net> (raw)
In-Reply-To: <1100537017.19830.147.camel@localhost>
Andy Wingo wrote:
>On Sun, 2004-11-14 at 10:48 +0000, Neil Jerram wrote:
>
>
>>Rob Browning wrote:
>>
>>
>>> --with-built-in-load-path='("foo" default "bar")'
>>>
>>>
>>This looks good to me. If this option is not specified, I presume the
>>default load path is ("$prefix/share/guile/site"
>>"$prefix/share/guile/$effective_version" "$prefix/share/guile")
>>
>>
>
>This sounds good to me as well for 1.7, but with one reservation: there
>are hordes of linux users that just do ./configure; make; make install
>for all autoconf'd software they download. I don't want to have to tell
>each one of them to set --prefix if they want the program to actually
>work.
>
I'm not sure what you mean by setting --prefix each time. All that the
user needs to do is - once-off - add
(set! %load-path (cons "/usr/local/share/guile" %load-path))
to their .guile or the system init.scm. And if the user can do
./configure etc., I reckon they can do this.
(And who's to say that they haven't decided to install autoconf'd
software in /opt/local, for example?)
> This means, distributors must be made aware that guile should
>follow the system C compiler's conventions, so that users are not
>surprised.
>
>
Personally, I've been surprised in the past _by_ the C compiler's
conventions. I seem to recall having serious trouble with one version
of Gtk in /usr and another version in /usr/local, because /usr/local
comes _before_ /usr in the include path, but _after_ it in the linker
path! So - unless I was being really stupid at the time - not a good
example to follow.
>Furthermore, if they put a /usr/local dir in the path, it should be
>before the default paths.
>
>
I think it's probably unwise to set up a system so that ordering is
important. However, with the .guile/init.scm approach, the user has
complete control here.
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-11-18 19:54 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
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 [this message]
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=419CFE10.7090407@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@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).