From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org
Subject: Re: Where to install files?
Date: Thu, 13 Oct 2005 19:08:24 +0100 [thread overview]
Message-ID: <87mzld5lyf.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <rmimzlfg7xi.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "11 Oct 2005 15:39:05 -0400")
Greg Troxel <gdt@ir.bbn.com> writes:
>> > My own view is that a package configured with --prefix=/usr/foo should
>> > install files only under /usr/foo. This leads me with guile to want
>> > to extend load-path to include guile directories in other prefixes.
>>
>> On this point I think I disagree with you. I think there is value in
>> forcing all packages to be loaded - or at least bootstrapped - from a
>> known load-path that is defined by the Guile installation.
>
> To me it's not a question of value. /usr/pkg belongs to pkgsrc, and
> to first order other stuff (meaning unmanaged and unrecord stuff)
> should not be there.
I'm not sure we're actually disagreeing here. My scheme would support
locations other than under /usr/pkg, so it doesn't conflict with your
last sentence.
That said, I've now modified my proposal to allow locations to be
added dynamically as you've suggested. I'll post that a little later.
> It's an autoconf (configure script really) directive, or perhaps one
> that's commonly added, meant to specify where config files go,
> defaulting to $(prefix)/etc or $(prefix)/etc/PACKAGE, but commonly
> used to force things to /etc/PACKAGE, especially on systems where
> people want that.
Thanks.
> I kind of like having several standard places within a prefix, as seen
> on NetBSD now:
>
> guile> %load-path
> ("/usr/pkg/share/guile/site" "/usr/pkg/share/guile/1.6"
> "/usr/pkg/share/guile" ".")
>
> Or rather, if that continues, I'd like to specify extra prefixes, with
> the load path being the cross product of within-prefix places and
> prefixes. But perhaps also single dirs.
That sounds too complicated to me! And my way already allows you to
have .../1.6 and .../site when you want them.
> I'd like a load-path directory, with files whose names are irrelevant
> but whose contets are dirs to add to the load path. This is
> pkg-friendly since they can be deleted and added automatically without
> merge/editing issues, using the fs to represent set semantics.
>
>> > It might also be nice to have a run-time method to
>> >
>> > guile-configer --addsearchprefix=/usr/bar
>> >
>> > so that someone building another package to /usr/bar can invoke this
>> > on the system guile to hook in the new path.
My new proposal isn't organized exactly as you suggest, but it allows
the same operations.
Regards,
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-10-13 18:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 19:29 Where to install files? Neil Jerram
2005-10-10 21:34 ` Kevin Ryde
2005-10-10 22:54 ` Neil Jerram
2005-10-11 0:18 ` Greg Troxel
2005-10-11 18:42 ` Neil Jerram
2005-10-11 19:39 ` Greg Troxel
2005-10-13 18:08 ` Neil Jerram [this message]
2005-10-12 8:29 ` Ludovic Courtès
2005-10-13 18:19 ` 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=87mzld5lyf.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).