From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Rewriting inputs and ’arguments’ after patch #43578
Date: Mon, 5 Oct 2020 16:17:10 +0200 [thread overview]
Message-ID: <CAJ3okZ3eE07WCQVLxGG-jBN+eecu8RYJC9yWQDdUU3Ga7wz-ww@mail.gmail.com> (raw)
In-Reply-To: <87zh50yeeb.fsf@gnu.org>
Hi Ludo,
On Mon, 5 Oct 2020 at 15:46, Ludovic Courtès <ludo@gnu.org> wrote:
> > Therefore, it is not possible to rewrite this “inputs“ (using the patch
> > [1]), as the dry-run shows:
> >
> > $ guix build emacs-magit --with-input=emacs-no-x=emacs-next -n
>
> AFAICS, it’s working as expected:
>
> --8<---------------cut here---------------start------------->8---
> $ guix gc --references $(guix build emacs-magit --with-input=emacs-no-x=emacs-next -d --no-grafts) |grep emacs-next
> /gnu/store/8ffjg2961x30171i24pl7j9wafcbli2b-emacs-next-28.0.50.1-0.2ea3466.drv
> $ guix gc --references $(guix build emacs-magit --with-input=emacs-no-x=emacs-next -d --no-grafts) |grep emacs-no-x
> --8<---------------cut here---------------end--------------->8---
Hum? I believe what I see... I am sure about my previous example and
your example also speaks by itself... Therefore, the most probable
seems to be a mistake between my keyboard and my chair. :-)
Sorry for the noise.
> Now, there dependencies in the graph that depend on ‘emacs-minimal’
> instead of ‘emacs-no-x’, so you’d probably also need to replace those.
Yep! That's the point of 'package-with-emacs-next'.
Cheers,
simon
prev parent reply other threads:[~2020-10-05 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200923161253.2378-1-ludo@gnu.org>
2020-09-28 19:39 ` Rewriting inputs and ’arguments’ after patch #43578 zimoun
2020-10-05 13:46 ` Ludovic Courtès
2020-10-05 14:17 ` zimoun [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ3eE07WCQVLxGG-jBN+eecu8RYJC9yWQDdUU3Ga7wz-ww@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@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).