unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Tom Willemsen <tom@ryuslash.org>
To: guile-user@gnu.org
Subject: Multiple version
Date: Tue, 03 Apr 2012 02:16:20 +0200	[thread overview]
Message-ID: <m3ehs58yaz.fsf@ryuslash.org> (raw)

Hey everyone,

I was wondering if it's possible to have guile 1.8 and guile 2.0
installed on the same system? I remember reading in the documentation
that it is, but I haven't been able to pull it off yet, except by using
different --prefix values for each.

The problem is that the distro I'm using (Archlinux) has guile 1.8 in
its repository and certain applications (like xbindkeys and freetalk)
still depend on it being this version. There are also at least two
packages in the Arch User Repository that provide guile 2.0, but these
both conflict with 1.8, so I can't yet install both.

I've tried a couple of times: I've used the --program-suffix argument to
make all binaries end with 2 (guile2, guild2, etc.), kind of like Python
does, but this doesn't help with the symlink of guile-tools (for
backwards compatibility). The --infodir argument is useful for keeping
the documentation seperate. That still leaves guile.m4.

I don't know enough about the autotools to know what to do with
guile.m4. Does automake/autoconf expect the file name to match
something, or does it only look at the definitions inside, in which case
it could simply be moved.

I've been looking at it for a while now and I'd really just like to know
if it's possibly to have both on the system and be able to use
everything in the 'regular' way.

I hope my question is clear. Thanks in advance!

Cheers,
Tom



             reply	other threads:[~2012-04-03  0:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03  0:16 Tom Willemsen [this message]
2012-04-03  0:32 ` Multiple version Greg Troxel
2012-04-03  7:48   ` Tom Willemsen
2012-04-03 16:47     ` 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=m3ehs58yaz.fsf@ryuslash.org \
    --to=tom@ryuslash.org \
    --cc=guile-user@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).