unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Cyprien Nicolas <c.nicolas@gmail.com>
To: 11451@debbugs.gnu.org
Subject: bug#11451: guile-2.0.5, guile-tools does not honor --program-suffix=
Date: Fri, 11 May 2012 14:14:58 +0200	[thread overview]
Message-ID: <4FAD02C2.6060202@gmail.com> (raw)

Hello guilers,

I'm working on provinding guile-2.0 in Gentoo. We choose to provide both
guile-1.8 and guile-2.0, as some programs have not been ported to
guile-2.0 (and some seems to have dead upstream).

In order to have both versions installed in /usr at the same
time, I make use of --program-suffix=-${MAJOR} during configure (MAJOR
being either 1.8 or 2.0). We provide a script that create symlinks for
guile binaries targeting either 1.8 or 2.0, update environment
(GUILE_LOAD_PATH), and even a symlink for the manpage.
This almost work out of the box, except for guile.m4, which is renamed
to guile-${MAJOR}.m4 at install time, and a symlink is handled by the
above script.


Two days ago, I tried to bump our guile ebuild from 2.0.1 to 2.0.5,
and I notice that guile-tools was renamed to guild. Well, this is not an
issue, I just have to update the above cited script to make the right links.


My issue is that the build system provides a symlink 'guile-tools' which
points to guild-2.0. And that symlink does not respect
--program-suffix=, thus our package manager complains about guile-tools
already existing in the installation directory.

I see two possibilities from here :
- make that symlink honoring --program-suffix;
- add a build option to tell the configure script that I don't want that
symlink (it will be created by our script).


Thanks

-- 
,Cyprien





             reply	other threads:[~2012-05-11 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-11 12:14 Cyprien Nicolas [this message]
2012-05-14 17:22 ` bug#11451: guile-2.0.5, guile-tools does not honor --program-suffix= Ludovic Courtès

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=4FAD02C2.6060202@gmail.com \
    --to=c.nicolas@gmail.com \
    --cc=11451@debbugs.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).