From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-user@gnu.org
Subject: Re: Modified load-path proposal
Date: Mon, 31 Oct 2005 19:20:35 +0000 [thread overview]
Message-ID: <87pspl1ojg.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87oe56zhus.fsf@zip.com.au> (Kevin Ryde's message of "Mon, 31 Oct 2005 10:48:43 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> What advantage is this over putting a symlink in /usr/share/guile/site
> to point to this alternate location?
Nothing really compelling, perhaps, but...
- some OSs don't have symlinks (i.e. Windows)
- the symlink approach doesn't work if a package installed with one
prefix wants to install (database mysql) and a different package
with a different prefix wants to install (database postgres)
- in my view, installing an init.d file (under $sysconfdir) feels less
polluting of the distribution-managed part of the filesystem than
putting a symlink into /usr/share/guile/site.
> What is the wherever/my/scheme/files/are directory likely to be?
> Guile library packages wouldn't be sprayed randomly across all four
> corners of the disk would they?
In practice I would guess not. Most distribution-managed packages
would go into /usr/share/guile, and most home-built packages into
/usr/local/share/guile, I'd guess. What is your concern, though?
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-31 19:20 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 18:21 Modified load-path proposal Neil Jerram
2005-10-13 18:40 ` Greg Troxel
2005-10-13 22:08 ` Neil Jerram
2005-10-14 0:37 ` Greg Troxel
2005-10-14 1:28 ` Andreas Rottmann
2005-10-15 11:17 ` Neil Jerram
2005-10-15 15:03 ` Greg Troxel
2005-10-15 17:53 ` Neil Jerram
2005-10-22 23:16 ` Kevin Ryde
2005-10-28 17:45 ` Neil Jerram
2005-10-30 18:04 ` Neil Jerram
2005-10-30 18:15 ` Tomas Zerolo
2005-10-30 20:37 ` Thien-Thi Nguyen
2005-10-30 22:59 ` Neil Jerram
2005-10-31 10:55 ` Thien-Thi Nguyen
2005-10-31 19:22 ` Neil Jerram
2005-11-08 12:37 ` Thien-Thi Nguyen
2005-10-31 13:17 ` Tomas Zerolo
2005-10-30 23:48 ` Kevin Ryde
2005-10-31 13:20 ` Tomas Zerolo
2005-10-31 19:20 ` Neil Jerram [this message]
2005-10-31 23:54 ` Kevin Ryde
2005-11-12 9:47 ` Neil Jerram
2005-11-01 23:31 ` Vorfeed Canal
2005-11-12 17:54 ` Neil Jerram
2005-11-02 8:44 ` Ludovic Courtès
2005-12-03 13:05 ` Neil Jerram
2005-12-13 8:38 ` Ludovic Courtès
2005-12-16 0:16 ` Neil Jerram
2005-12-16 1:00 ` Neil Jerram
2005-12-16 9:55 ` Ludovic Courtès
2006-01-07 13:37 ` Neil Jerram
2006-01-11 4:49 ` steve tell
2006-01-12 18:01 ` Neil Jerram
2005-10-15 11:24 ` Neil Jerram
2005-10-15 15:01 ` Greg Troxel
2005-10-15 17:49 ` Neil Jerram
2005-10-14 7:24 ` Ludovic Courtès
2005-10-15 11:55 ` Neil Jerram
2005-10-15 15:40 ` Greg Troxel
2005-10-17 8:04 ` Ludovic Courtès
2005-10-17 17:52 ` Greg Troxel
2005-10-18 8:23 ` Search path for C libraries Ludovic Courtès
2005-10-18 10:12 ` Vorfeed Canal
2005-10-17 17:54 ` Modified load-path proposal Neil Jerram
2005-10-18 7:57 ` Ludovic Courtès
2005-10-19 22:30 ` Neil Jerram
2005-10-20 7:56 ` Vorfeed Canal
2005-10-20 8:05 ` Ludovic Courtès
2005-10-20 22:23 ` Neil Jerram
2005-10-21 7:59 ` Ludovic Courtès
2005-10-17 18:10 ` Neil Jerram
2005-10-18 16:16 ` Greg Troxel
2005-10-18 21:24 ` Vorfeed Canal
2005-10-19 22:29 ` 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=87pspl1ojg.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).