From: Greg Troxel <gdt@ir.bbn.com>
To: Mike Gran <spk121@yahoo.com>
Cc: Gule User <guile-user@gnu.org>
Subject: Re: Autoconf test for site scheme files
Date: Tue, 07 Aug 2007 12:35:05 -0400 [thread overview]
Message-ID: <rmik5s7xpza.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <140901.61872.qm@web37904.mail.mud.yahoo.com> (Mike Gran's message of "Tue, 7 Aug 2007 08:42:12 -0700 (PDT)")
The hard question is whether you want the site directory in guile's
prefix, or the corresponding place in your prefix, assuming they are
different. I have tended to use the corresponding place in my prefix,
and then to either add to load path or symlink my subdir into guile's
site directory.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2007-08-07 16:35 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 [this message]
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
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=rmik5s7xpza.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-user@gnu.org \
--cc=spk121@yahoo.com \
/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).