unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: nigko <nigko.yerden@gmail.com>, help-guix@gnu.org
Subject: Re: 'guix install' downloads all outputs for packages with cmake build system.
Date: Tue, 10 Dec 2024 15:49:21 +0100	[thread overview]
Message-ID: <87h67bzj7y.fsf@gmail.com> (raw)
In-Reply-To: <CAO356aGRDD53rFr76z9Q11Ev6kamvGoV-SiNQZaPqkiKMjCW3Q@mail.gmail.com>

Hi,

On Wed, 09 Oct 2024 at 18:55, nigko <nigko.yerden@gmail.com> wrote:

> ------------------------------------------------------------------------
> # don't forget to insure that /gnu/store does not already contain
> # x265's static output before running this command:
> $ guix install x265
> The following package will be installed:
>    x265 3.5
> ...
> 2,8 MB will be downloaded
>  x265-3.5-static  1.3MiB
>  x265-3.5  1.4MiB
> ...
> ------------------------------------------------------------------------

Hum. I am not able to reproduce.

First, let be sure nothing is already in the store.

--8<---------------cut here---------------start------------->8---
$ guix gc --list-dead | grep x265-3.5-static
finding garbage collector roots...
determining live/dead paths...

$ guix gc --list-live | grep x265-3.5-static
finding garbage collector roots...
determining live/dead paths...

$ find /gnu/store -maxdepth 1 -type d -name "x256-3.5-static" -print
--8<---------------cut here---------------end--------------->8---

Second, try to install:

--8<---------------cut here---------------start------------->8---
$ guix install x265 --dry-run
guix install: warning: Your Guix installation is 92 days old.
guix install: warning: Consider running 'guix pull' followed by
'guix package -u' to get up-to-date packages and security updates.

The following package would be installed:
   x265 3.5
--8<---------------cut here---------------end--------------->8---

And ’static’ output does not seem required.

> An interesting bit about this abnormal behavior was gained from the
> discusstion on IRC. It turns out that the command
> 'guix install --no-grafts <package>' with --no-grafts flag does not
> download all the outputs of the package but only the "out" output,
> as one would expect from 'guix install' command. So the issue seems
> to be related to grafts. What do you think?

Could you give your Guix revision?  Mine is 056910e; please note x265
had not be modified since a while and the package isn’t grafted.

--8<---------------cut here---------------start------------->8---
$ guix build x265 -d
/gnu/store/5v0d3wf3rhy69i1fl0jdchpmwy5wxbas-x265-3.5.drv

$ guix build x265 -d --no-grafts
/gnu/store/5v0d3wf3rhy69i1fl0jdchpmwy5wxbas-x265-3.5.drv
--8<---------------cut here---------------end--------------->8---

Hum, I don’t know where could the observed behaviour come from?

Cheers,
simon


  reply	other threads:[~2024-12-10 16:50 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 [this message]
2024-12-10 18:28   ` Nigko Yerden
2024-12-11  8:54     ` Rutherther
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=87h67bzj7y.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=nigko.yerden@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).