From: ng0 <ng0@we.make.ritual.n0.is>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>,
help-guix <help-guix@gnu.org>
Subject: Re: Why does installing icedtea-1.13.12 install the docs and jdk, too?
Date: Fri, 16 Sep 2016 14:49:41 +0000 [thread overview]
Message-ID: <87poo3x5kq.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <57DC03A3.5050507@crazy-compilers.com>
Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
> Am 16.09.2016 um 16:05 schrieb ng0:
>> I think you are confusing installation with downloading.
>
> Maybe :-) But I'd expect that only packages to be installed are
> downloaded. Otherwise this would be a wast of time and bandwidth.
There's a separation between packages and outputs. gnunet-svn is a
different package than gnunet, git-sendemail and git-svn are contained
in outputs of git (named 'sendemail' and 'svn'). They are not separated
like for example Debian does it with their -dev version packages.
For the exact reasons someone else has to explain. I guess it's
something about grafting, reproducibility, source provision etc.
>> if (I have not checked it) icedtea is just one package with multiple outputs,
> it is.
>
>> all outputs will be downloaded
>
> But why? I do not see any reason for downloading packages which their
> are neither requested nor installed. If all outputs are downloaded, what
> should be the sense of having different outputs?
>
> --
> Regards
> Hartmut Goebel
>
> | Hartmut Goebel | h.goebel@crazy-compilers.com |
> | www.crazy-compilers.com | compilers which you thought are impossible |
>
>
--
ng0
next prev parent reply other threads:[~2016-09-16 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 11:42 Why does installing icedtea-1.13.12 install the docs and jdk, too? Hartmut Goebel
2016-09-16 14:05 ` ng0
2016-09-16 14:37 ` Hartmut Goebel
2016-09-16 14:49 ` ng0 [this message]
2016-09-16 14:57 ` Hartmut Goebel
2016-09-24 0:32 ` Leo Famulari
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87poo3x5kq.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=h.goebel@crazy-compilers.com \
--cc=help-guix@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.