unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Subject: Re: Another load path idea
Date: Fri, 27 Jan 2006 09:57:25 +0100	[thread overview]
Message-ID: <87zmlit5e2.fsf@laas.fr> (raw)
In-Reply-To: <87irs68uie.fsf@zip.com.au> (Kevin Ryde's message of "Fri, 27 Jan 2006 10:00:25 +1100")

Hi,

Kevin Ryde <user42@zip.com.au> writes:

> I think it will be enough to,
>
> 1. Add /usr/local into the default %load-path.
>
> 2. Put a note in the manual inviting package builders to augment
>    %load-path further if they wish, eg. for /opt.  (By patching
>    boot-9.scm I would think.)
>
> 3. Put a note in the manual encouraging the use of /site by sysadmins,
>    but with an invitation to extend %load-path if they've got good
>    reason for violating the usual setup.

As I understand it, the whole point of this discussion is about
providing mechanisms to allow the initial value of `%load-path' to be
easily and cleanly customized, i.e., not by "patching boot-9.scm".  ;-)

Then there is another question which is: _who_ performs this
customization and _when_?  Neil (and I) initially suggested that this
could be done automatically by packages themselves at installation-time.
You suggest, OTOH, that this should be done manually by the sysadmin,
after they installed a package in some "unusual" path.

In either case, we still need (i) a config file holding the default
value of `%load-path', (ii) a script to manipulate that file (i.e., to
add/remove directories from it).

Thanks,
Ludovic.


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2006-01-27  8:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-07 13:42 Another load path idea Neil Jerram
2006-01-12  9:38 ` Ludovic Courtès
2006-01-12 17:44   ` Neil Jerram
2006-01-19  9:21     ` Ludovic Courtès
2006-01-20 21:21       ` Kevin Ryde
2006-01-21  9:01       ` Neil Jerram
2006-01-22 15:38         ` Andy Wingo
2006-01-26  0:55           ` Kevin Ryde
2006-01-26  8:39             ` Ludovic Courtès
2006-01-26 20:19           ` Neil Jerram
2006-01-26 23:00             ` Kevin Ryde
2006-01-27  8:57               ` Ludovic Courtès [this message]
2006-01-28  0:39                 ` Kevin Ryde
2006-01-30  9:11                   ` Ludovic Courtès
2006-02-04 16:44                     ` Neil Jerram
2006-01-29 22:39               ` Greg Troxel
2006-01-31 20:23                 ` Kevin Ryde
2006-01-31 20:58                   ` Greg Troxel
2006-01-23  8:27         ` Ludovic Courtès
2006-01-23 20:04           ` 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=87zmlit5e2.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    /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).