From: zimoun <zimon.toutoune@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Specifying dependencies among package outputs?
Date: Thu, 15 Oct 2020 13:44:00 +0200 [thread overview]
Message-ID: <CAJ3okZ3-+dmYNPD87XUEf7_WAy4hj8=45zidjS_Rg1X9U-vB7g@mail.gmail.com> (raw)
In-Reply-To: <87y2k8mihx.fsf@nckx>
Hi Tobias,
On Thu, 15 Oct 2020 at 02:38, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
> Well, yes, but probably not in the way you mean: they aren't
> specified at all. Oh dear, nckx's responding to a question about
> ‘dependencies’. Apologies to those who know what's coming.
[...]
> If you apply the patch below you'll see (e.g., with ‘guix size’)
> that installing only knot:tools will pull in knot{:out,:lib}
> without any human-made hints to that effect.
Wow! Thank you for the detailed explanation. I have also been
puzzled by this and my mind was still a bit foggy on the topic. Now
all clear! :-)
> Attached patch:
>
> $ guix size /gnu/store/...-knot-3.0.1-doc
> total: 0.2 MiB (no references)
> $ guix size /gnu/store/...-knot-3.0.1-lib
> total: 145.0 MiB (self: 2.4 MiB)
> $ guix size /gnu/store/...-knot-3.0.1
> total: 171.1 MiB (self: 5.2 MiB; refers to :lib)
> $ guix size /gnu/store/...-knot-3.0.1-tools
> total: 164.9 MiB (self: 0.4 MiB; refers to :lib)
>
> Old monolithic knot:
>
> $ guix size /gnu/store/...-knot-3.0.1
> total: 171.5 MiB (self: 8.0 MiB)
These numbers are self explanatory for me. Maybe this example could
go to the Cookbook?
All the best,
simon
next prev parent reply other threads:[~2020-10-15 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 22:32 Specifying dependencies among package outputs? Simon South
2020-10-15 0:07 ` Julien Lepiller
2020-10-15 0:37 ` Tobias Geerinckx-Rice
2020-10-15 0:43 ` Tobias Geerinckx-Rice
2020-10-15 11:44 ` zimoun [this message]
2020-10-15 14:54 ` Simon South
2020-10-15 22:26 ` Tobias Geerinckx-Rice
2020-10-15 23:45 ` Simon South
2020-10-16 17:32 ` Tobias Geerinckx-Rice
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='CAJ3okZ3-+dmYNPD87XUEf7_WAy4hj8=45zidjS_Rg1X9U-vB7g@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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).