unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: pkill9 <pkill9@runbox.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 43984@debbugs.gnu.org
Subject: bug#43984: `--with-graft=...` doesn't work with packages of different length name/version
Date: Thu, 15 Oct 2020 19:50:13 +0100	[thread overview]
Message-ID: <20201015195013.335eaefd@runbox.com> (raw)
In-Reply-To: <87wnzsapwh.fsf@gnu.org>

> > Maybe if the length/version is different, then a symlink could be
> > created in the store pointing to the new dependency, with a
> > name/version that matches the length of the original dependency's
> > store name? Perhaps this new name/version could be something like
> > /gnu/store/...-original-dependency-name-gggggg, where 'g..' matches
> > the length of the version of the original dependency. The many 'g's
> > would make it clear that it is a graft. Then if someone looks in
> > the store, they would see it's a symlink too.  
> 
> That only works if the new name is shorter than the old name though.
> When the new name is longer (which is a more common case in our
> experience when introducing package replacements, typically because
> the new version string is longer), nothing can be done.

I'm confused about what you mean. Why would it matter if the new
name is longer than the old name?




  reply	other threads:[~2020-10-15 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14  0:55 bug#43984: `--with-graft=...` doesn't work with packages of different length name/version pkill9
2020-10-15  7:50 ` Ludovic Courtès
2020-10-15 18:50   ` pkill9 [this message]
2020-10-16  9:31     ` Ludovic Courtès
2020-10-17  1:03       ` pkill9
2020-10-20 21:29         ` Ludovic Courtès
2020-10-20 22:34           ` Mark H Weaver
2020-10-21  8:45             ` 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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20201015195013.335eaefd@runbox.com \
    --to=pkill9@runbox.com \
    --cc=43984@debbugs.gnu.org \
    --cc=ludo@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.
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).