From: Rutherther <rutherther@ditigal.xyz>
To: Thomas Schwinge <tschwinge@baylibre.com>
Cc: guix-devel@gnu.org
Cc: help-guix@gnu.org
Subject: Re: 'guix build [P]' followed by 'guix install /gnu/store/[...]' vs. 'guix install [P]'
Date: Thu, 07 Nov 2024 19:21:52 +0100 [thread overview]
Message-ID: <87ldxuaoqn.fsf@ditigal.xyz> (raw)
In-Reply-To: <87ttcj2j45.fsf@euler.schwinge.ddns.net>
Hello,
> How do I, by the way, programmatically get from the 'guix build' list of
> (here: three) outputs to the main ("out") output? Via
the outputs work something like this: when the package is being built
the builder scripts build everything. At the end, something
is copied to out output, something to debug output, and something to
static output.
So when you are building the package locally, you cannot just tell guix
build to produce only one of those outputs. Because the phases are
already coded in a way to produce all of them.
If you really wanted to not build them, you would have to change
the package definition itself. Specifically with gcc-toolchain it
would be quite easy as it's only sort of a wrapper package that
builds together gcc and libc. The static/debug outputs
are actually just copied outputs of those.
> (Is there a fundamental reason for not allowing that, or just not yet
> implemented?)
So yeah, there is. But sometimes substitutes will give you only
one output you request. (I am not sure what the condition is,
seems that for some build systems it's possible), this of course
applies only to packages that have substitutes and only if you use
command like guix shell / guix install.
Additionally, if you are only concerned about the size it takes up in
store, you can guix gc those paths right after the build.
Regards,
Rutherther
next prev parent reply other threads:[~2024-11-07 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 17:10 'guix build [P]' followed by 'guix install /gnu/store/[...]' vs. 'guix install [P]' Thomas Schwinge
2024-11-07 14:50 ` Thomas Schwinge
2024-11-07 18:21 ` Rutherther [this message]
2024-11-09 23:31 ` Ludovic Courtès
2024-11-10 10:02 ` Thomas Schwinge
2024-11-14 10:00 ` 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=87ldxuaoqn.fsf@ditigal.xyz \
--to=rutherther@ditigal.xyz \
--cc=guix-devel@gnu.org \
--cc=tschwinge@baylibre.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).