From: Greg Troxel <gdt@ir.bbn.com>
To: Tom Willemsen <tom@ryuslash.org>
Cc: guile-user@gnu.org
Subject: Re: Multiple version
Date: Tue, 03 Apr 2012 12:47:07 -0400 [thread overview]
Message-ID: <rmifwckhies.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <m3limd9rxi.fsf@ryuslash.org> (Tom Willemsen's message of "Tue, 03 Apr 2012 09:48:41 +0200")
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
I think that aclocal looks for files that define needed macros, so you'd
still get a conflict even if the file is renamed.
But if I write something that depends on guile, would I have to change
anything in my scripts to use guile 2.0 if I've installed the file as,
for example, guile2.m4?
Not if
a) your code actually builds with guile 2, and
b) the aclocal m4 code with 1.8 finds guile2 ok
now that guile does pkg-config, i would think that's preferable, but if
a package installs scheme files into share/guile/site then it may not be
adequate.
Your programs that use guile should just be able to do
--with-guile=/usr/guile2 or some such.
If you want to fix this, I think it only makes sense to get patches into
guile to make program-suffix work 100%, and otherwise you risk being in
a wet-noodle-pushing exercise.
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
prev parent reply other threads:[~2012-04-03 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 0:16 Multiple version Tom Willemsen
2012-04-03 0:32 ` Greg Troxel
2012-04-03 7:48 ` Tom Willemsen
2012-04-03 16:47 ` Greg Troxel [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=rmifwckhies.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=guile-user@gnu.org \
--cc=tom@ryuslash.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).