From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: meiyo.peng@gmail.com, 30265@debbugs.gnu.org
Subject: bug#30265: Fish shell has wrong path variables
Date: Fri, 21 Sep 2018 16:46:21 +0200 [thread overview]
Message-ID: <87y3buucw2.fsf@elephly.net> (raw)
In-Reply-To: <877ejeykro.fsf@ambrevar.xyz>
Pierre Neidhardt <mail@ambrevar.xyz> writes:
>> In practice only a subset of these grafts are applied because, for
>> instance, Fish doesn’t depend (directly or indirectly) on Ghostscript at
>> run time whereas it does depend on Perl:
>>
>> --8<---------------cut here---------------start------------->8---
>> $ guix gc -R $(guix build fish) | grep -E '(perl|ghostscript)'
>> /gnu/store/7ifc22sh86zblnzamqimgmv06idyx69v-perl-5.26.1
>> --8<---------------cut here---------------end--------------->8---
>
> Thanks for pointing out this nuance, I wasn't aware of it.
>
> But I still wonder: why is fish first built to
> vgrav12zra9zky21ahm4x1qg8g4v58fj... and then immediately grafted to
> avk637800w1n7z1z0hnzx80r0fpd6729... Why not building directly to
> avk637800w1n7z1z0hnzx80r0fpd6729...?
Grafting is independent of building a package. These are separate
derivations. The first derivation is merely about building the package
— it is unaware of the need for grafting.
The second derivation only performs the graft. All it knows about is
that it takes “vgrav12zra9zky21ahm4x1qg8g4v58fj” as an input and should
produce “avk637800w1n7z1z0hnzx80r0fpd6729”.
--
Ricardo
next prev parent reply other threads:[~2018-09-21 14:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-27 9:11 bug#30265: Fish shell has wrong path variables Meiyo Peng
2018-01-27 10:36 ` ng0
2018-01-27 16:25 ` Ludovic Courtès
2018-01-27 18:19 ` ng0
2018-01-27 12:19 ` Ricardo Wurmus
2018-01-27 13:45 ` Meiyo Peng
2018-01-27 14:13 ` Meiyo Peng
2018-09-19 9:09 ` Pierre Neidhardt
2018-09-19 20:39 ` Ludovic Courtès
2018-09-20 16:09 ` Pierre Neidhardt
2018-09-20 17:00 ` Ricardo Wurmus
2018-09-20 17:12 ` Pierre Neidhardt
2018-09-21 12:03 ` Ludovic Courtès
2018-09-21 12:05 ` Ludovic Courtès
2018-09-21 14:42 ` Pierre Neidhardt
2018-09-21 14:46 ` Ricardo Wurmus [this message]
2018-09-21 15:11 ` Pierre Neidhardt
2019-02-02 7:20 ` bug#30265: Fish embeds store file names in UCS-4/UTF-32 literal strings Meiyo Peng
2019-02-04 22:16 ` Ludovic Courtès
2020-03-30 6:29 ` John Soo
2022-10-07 19:42 ` Maxim Cournoyer
2022-10-07 19:43 ` Maxim Cournoyer
2022-10-07 19:44 ` John Soo
2022-10-07 20:57 ` Mark H Weaver
2022-10-10 3:38 ` Maxim Cournoyer
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=87y3buucw2.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=30265@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
--cc=meiyo.peng@gmail.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.
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).