From: Jack Hill <jackhill@jackhill.us>
To: Marius Bakke <mbakke@fastmail.com>
Cc: help-guix@gnu.org
Subject: Re: Why are these derivations different?
Date: Mon, 10 Jun 2019 13:25:38 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1906101324070.5164@marsh.hcoop.net> (raw)
In-Reply-To: <878su9fzac.fsf@devup.no>
On Mon, 10 Jun 2019, Marius Bakke wrote:
>> What's really going on with --no-grafts. Is it that guix on my less
>> powerful host has never seen the the ungoogled-chromium version build
>> against the older dependencies, so doesn't accept the older version that
>> could be grafted? I guess, I'm not sure exactly what you mean by "fails to
>> realize the grafted derivation". Is that a bug?
>
> Sorry, just a lazy and poor attempt at explaining what's going on... :-)
No worries, I appreciate you taking the time to help me understand.
>> Sorry, I don't think that question was very clear. It probably means that
>> while I think I know what grafts are, I don't know enough about what's
>> going on to ask the question properly. I think this all could be summarized
>> as, "please explain more."
>
> Grafts are are ignored in some parts of Guix. In this case, if you
> inspect the profile derivation when doing 'guix install -n
> ungoogled-chromium', you can see that the computed profile.drv needs to
> produce the ungrafted ungoogled-chromium-x.y.z.drv, because the
> profile-builder references the _ungrafted_ package.
>
> I'm not sure of the exact mechanics that follow, but I guess grafts are
> only computed afterwards, recursively, for the generated profile.
Ok, thank help. Thank you.
Jack
prev parent reply other threads:[~2019-06-10 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 14:49 Why are these derivations different? Jack Hill
2019-06-08 20:45 ` Marius Bakke
2019-06-09 2:43 ` Jack Hill
2019-06-10 11:35 ` Marius Bakke
2019-06-10 17:25 ` Jack Hill [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=alpine.DEB.2.20.1906101324070.5164@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=help-guix@gnu.org \
--cc=mbakke@fastmail.com \
/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).