unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Jon Wilson <jsw@wilsonjc.us>
To: guile-user@gnu.org
Subject: Re: Autoconf test for site scheme files
Date: Sun, 12 Aug 2007 00:27:07 -0400	[thread overview]
Message-ID: <46BE8C1B.8090308@wilsonjc.us> (raw)
In-Reply-To: <87wsw64hn0.fsf@chbouib.org>

Ludovic Courtès wrote:
> Mike Gran <spk121@yahoo.com> writes:
>> This brings up another question.  Should %load-path should generally
>> include /usr/local/share/guile/site by default?
>>
>> Arguments in favor: it would keep symmetry with the emacs $(lispdir)
>> directory as described in the GNU coding standards. [1] 
>> Philosophically, can something be "site"-specific and not be "local"?
>>     
> OTOH, why have two `site' directories by default?
>   
Using ubuntu, apt installs packages under /usr.  When I find something 
that either isn't up to date enough or doesn't exist in the ubuntu 
repos, I build it from source.  In that case, I either install to /opt 
or to /usr/local.  Sometimes this includes packages which want to 
install guile modules (currently, it includes guile!).  I try to keep 
/usr untouched except by apt, but it does make sense to have these 
modules in a `site' directory.

For instance, I have guile-lib installed from the ubuntu package to 
/usr/share/guile/site, and I have guile-gdbm installed to 
/usr/local/share/guile/site.  I think this constitutes a pragmatic 
(although perhaps not good?) reason to have two site dirs.

Regards,
Jon



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


  parent reply	other threads:[~2007-08-12  4:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 15:42 Autoconf test for site scheme files Mike Gran
2007-08-07 16:35 ` Greg Troxel
2007-08-07 16:52   ` Mike Gran
2007-08-08  7:20     ` Ludovic Courtès
2007-08-08 15:03       ` Mike Gran
2007-08-12  4:27       ` Jon Wilson [this message]
2007-08-12 11:43         ` Greg Troxel

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=46BE8C1B.8090308@wilsonjc.us \
    --to=jsw@wilsonjc.us \
    --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).