From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: PATCH for guile-readline/Makefile.am
Date: Tue, 13 Jan 2004 11:38:36 -0600 [thread overview]
Message-ID: <87k73vagv7.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87d69rz7or.fsf@zagadka.ping.de> (Marius Vollmer's message of "Sun, 11 Jan 2004 00:48:36 +0100")
Marius Vollmer <mvo@zagadka.de> writes:
> What about moving readline.scm to ice-9/readline.scm in the source
> tree? I.e., we place readline.scm directly in ice-9 and remove it
> from guile-readline once and for all. Then the symlink is not
> needed.
That seems OK.
Also, if we really did want to keep everything in guile-readline/,
then I suspect we could just move readline.scm to a new subdir,
i.e. guile-readline/ice-9/readline.scm, and then augment the
pre-inst-guile GUILE_LOAD_PATH as appropriate. I've done something
similar for other projects that were basically supposed to be
"unioned" with existing GUILE_LOAD_PATH dirs.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-13 17:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 21:56 PATCH for guile-readline/Makefile.am Richard Todd
2004-01-10 19:41 ` Kevin Ryde
2004-01-10 20:57 ` Marius Vollmer
2004-01-10 23:48 ` Marius Vollmer
2004-01-13 17:38 ` Rob Browning [this message]
2004-01-14 0:51 ` Marius Vollmer
2004-01-14 7:41 ` Rob Browning
2004-01-19 18:13 ` Rob Browning
2004-01-19 22:29 ` Kevin Ryde
2004-01-20 6:23 ` Rob Browning
2004-01-20 6:49 ` Rob Browning
2004-01-21 21:31 ` Kevin Ryde
2004-01-14 20:50 ` Kevin Ryde
2004-01-15 1:17 ` Richard Todd
2004-01-16 6:42 ` Rob Browning
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=87k73vagv7.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@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).