From: Andy Wingo <wingo@pobox.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-guile@gnu.org
Subject: Re: guile-config deprecated or not?
Date: Mon, 21 Feb 2011 22:27:00 +0100 [thread overview]
Message-ID: <m3lj19xemz.fsf@unquote.localdomain> (raw)
In-Reply-To: <201102210000.33044.bruno@clisp.org> (Bruno Haible's message of "Mon, 21 Feb 2011 00:00:32 +0100")
Hi Bruno,
On Mon 21 Feb 2011 00:00, Bruno Haible <bruno@clisp.org> writes:
> Andy Wingo wrote:
>> > So, is guile-config deprecated or not?
>>
>> It is deprecated, yes. I have fixed the examples to use pkg-config. I
>> did not fix guile.m4 though, as the current system does have the
>> characteristic of selecting for whatever version of Guile you have
>> installed
>
> This is a good property: It uses the installed guile that matches the
> 'guile-config' program that is found in PATH.
>
>> though not allowing you to choose.
>
> Huh? The user can influence which guile installation is chosen by
> modifying PATH.
>
> Without guile-config, the user would have to manipulate PKG_CONFIG_PATH in
> order to get the "right" guile used (from his perspective). I would vote
> for undeprecating guile-config for this reason.
This is a misunderstanding. Guile is parallel-installable with regards
to different "effective versions". So Guile 2.2 will be parallel
installable, in the same prefix and path, as Guile 2.0. Our binaries
currently collide, but the headers, libraries, scheme files, and
compiled scheme files do not.
So one might select pkg-config --libs guile-2.0.pc, or guile-2.2.pc.
I do agree that it makes sense to ask "give me the latest Guile", but
one may do that in other ways (pkg-config --list-all | grep guile-.-.,
explicit version list, guile -c '(display (effective-version))', etc.).
>> Ideally we can figure out a way to merge in your -rpath code into
>> pkg.m4.
>
> Please keep me in the loop when you start working on this.
Heh, understood. I don't have much energy for this right now though.
Regards,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2011-02-21 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 14:05 guile-config deprecated or not? Bruno Haible
2011-02-20 21:12 ` Andy Wingo
2011-02-20 23:00 ` Bruno Haible
2011-02-21 21:27 ` Andy Wingo [this message]
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=m3lj19xemz.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bruno@clisp.org \
--cc=bug-guile@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).