From: Andy Wingo <wingo@pobox.com>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: 10488@debbugs.gnu.org
Subject: bug#10488: guile-config deprecation?
Date: Sat, 09 Mar 2013 11:28:21 +0100 [thread overview]
Message-ID: <8738w43m0q.fsf@pobox.com> (raw)
In-Reply-To: <878v65q84t.fsf@zigzag.favinet> (Thien-Thi Nguyen's message of "Sun, 03 Mar 2013 08:01:38 +0100")
Hi,
On Sun 03 Mar 2013 08:01, Thien-Thi Nguyen <ttn@gnuvola.org> writes:
> () Andy Wingo <wingo@pobox.com>
> () Sat, 02 Mar 2013 19:42:19 +0100
>
> I pushed it to a branch a year ago but it never got review. Here's
> the patch, rebased and attached. I'll commit it soon if there are no
> objections.
>
> Not an objection, but a suggestion: If the purpose of the code is to
> select a Guile version, why not call it guile-sel.m4 (or somesuch),
> and distribute it alongside guile.m4?
With parallel installation, there is no obvious global choice of which
version of Guile is the right one. Projects should choose, explicitly.
A guile.m4 update will adjust the default search order, but projects
should probably also bundle a copy of guile.m4 to prevent bug reports
about inexplicable autoconf errors. So even if the system guile.m4 is
updated, a typical project's choice of version does not change.
There is also the difficulty that Guile provides two APIs: one for C and
one for Scheme. When guile.m4 goes to look for the details of those
APIs (e.g. the guild binary, and the libguile library), they need to
come from the same Guile installation. For this reason guile.m4 should
be aware of which choice the user has made, and have an easy way of
correlating C and Scheme API.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-03-09 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 18:42 bug#10488: guile-config deprecation? Mike Gran
2012-02-02 13:41 ` Andy Wingo
2012-02-02 18:49 ` dsmich
2012-02-02 20:42 ` Andy Wingo
2012-03-30 18:05 ` Andy Wingo
2013-03-02 18:42 ` Andy Wingo
2013-03-02 21:41 ` Ludovic Courtès
2013-03-09 10:20 ` Andy Wingo
[not found] ` <878v65q84t.fsf@zigzag.favinet>
2013-03-09 10:28 ` Andy Wingo [this message]
2013-03-10 22:35 ` Andy Wingo
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=8738w43m0q.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=10488@debbugs.gnu.org \
--cc=ttn@gnuvola.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).