unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: "Zack Weinberg" <zack@owlfolio.org>
Cc: 64509@debbugs.gnu.org
Subject: bug#64509: Guile packages should install versioned aliases for binaries (guile-X.Y, guild-X.Y, etc.)
Date: Tue, 15 Aug 2023 23:33:47 +0200	[thread overview]
Message-ID: <87o7j86ldw.fsf@gnu.org> (raw)
In-Reply-To: <c33108af-e7b3-4f95-9624-9a702ade8f34@app.fastmail.com> (Zack Weinberg's message of "Fri, 07 Jul 2023 08:59:10 -0400")

Hi Zack,

"Zack Weinberg" <zack@owlfolio.org> skribis:

> The Guile packages currently install all their binaries under their
> basic name only, e.g.
>
> $ ls /gnu/store/4gvgcfdiz67wv04ihqfa8pqwzsb0qpv5-guile-3.0.9/bin
> /gnu/store/4gvgcfdiz67wv04ihqfa8pqwzsb0qpv5-guile-3.0.9/bin:
> guild  guile  guile-config  guile-snarf  guile-tools
>
> However, the Autoconf macro GUILE_PROGS (from guile.m4) looks first
> for a guile binary with a version number suffix (e.g. ‘guile-3.0’).
> If it finds one, then it looks *only* for a matching guild-X.Y and
> errors out if it can’t find that.  This is a problem for building Guix
> itself from source in a non-pure ‘guix shell -D guix’ on top of a
> foreign distro that provides a ‘guile-3.0’ binary but not the other
> four programs:

I think the solution is to use ‘guix shell -D guix -CP’: that’ll give
you a container, where /usr/bin/guile-3.0 isn’t accessible, which
ensures there’s no interference.

(FWIW this is what I do, even on Guix System, for my development
environments.)

Does that work for you?

If your distro doesn’t support unprivileged user namespaces, which ‘-C’
relies on, you can fall back to ‘--pure’.

Ludo’.




  reply	other threads:[~2023-08-15 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 12:59 bug#64509: Guile packages should install versioned aliases for binaries (guile-X.Y, guild-X.Y, etc.) Zack Weinberg
2023-08-15 21:33 ` Ludovic Courtès [this message]
2023-08-16 16:09   ` Zack Weinberg
2023-08-21  7:37   ` Janneke Nieuwenhuizen
2023-09-05 19:59     ` Zack Weinberg

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7j86ldw.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=64509@debbugs.gnu.org \
    --cc=zack@owlfolio.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).