From: Rutherther <rutherther@ditigal.xyz>
To: Nigko Yerden <nigko.yerden@gmail.com>
Cc: Simon Tournier <zimon.toutoune@gmail.com>, help-guix@gnu.org
Subject: Re: 'guix install' downloads all outputs for packages with cmake build system.
Date: Wed, 11 Dec 2024 09:54:54 +0100 [thread overview]
Message-ID: <875xnqppk1.fsf@ditigal.xyz> (raw)
In-Reply-To: <12c4d800-7667-40a3-a104-fc8f97b7f5f2@gmail.com>
Hello Nigko,
> Hello Simon,
> Now I'm on 47ab553178eb00d02ba9588ed1f7df44fb2f7c4c guix commit and
> still have the problem:
> ----begin-----------------------------------------------------------
> $ guix build x265 -d
You are building the package. I think I've already explained it on
the IRC few weeks ago: due to how guix is made, build always builds
all outputs. That is because when you are building the package,
there is just one build process and in middle of that process
some files are copied to other outputs. With `guix build`, you cannot
even specify the outputs. So even on substitution, you get all
of them. That's what you would get if nothing was substituted
and the build ran on your system.
> Moreover, since then I have realized that the problem is not specific
> to packages with cmake build system but concerns all packages with
> multiple outputs.
Yes, with guix build it is for all packages, is expected,
and there is likely no way around it. Please provide guix install
example, where this happens, that's what you reported as an issue earlier.
With install, you no longer need to get all outputs,
when you do not need to build the package,
so you should be able to get just one output as long as
it is substituted. So indeed, if install substitutes all outputs
for some packages, something is wrong and it should be possible to fix it.
Rutherther
Date: Wed, 11 Dec 2024 09:54:36 +0100
Message-ID: <878qsmppkj.fsf@ditigal.xyz>
next prev parent reply other threads:[~2024-12-11 8:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 13:55 'guix install' downloads all outputs for packages with cmake build system nigko
2024-12-10 14:49 ` Simon Tournier
2024-12-10 18:28 ` Nigko Yerden
2024-12-11 8:54 ` Rutherther [this message]
2024-12-11 11:42 ` nigko
2024-12-11 13:02 ` nigko
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=875xnqppk1.fsf@ditigal.xyz \
--to=rutherther@ditigal.xyz \
--cc=help-guix@gnu.org \
--cc=nigko.yerden@gmail.com \
--cc=zimon.toutoune@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.
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).