From: Leo Famulari <leo@famulari.name>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: help-guix <help-guix@gnu.org>, ng0 <ng0@we.make.ritual.n0.is>
Subject: Re: Why does installing icedtea-1.13.12 install the docs and jdk, too?
Date: Fri, 23 Sep 2016 20:32:59 -0400 [thread overview]
Message-ID: <20160924003259.GB24812@jasmine> (raw)
In-Reply-To: <57DC0848.50506@crazy-compilers.com>
On Fri, Sep 16, 2016 at 04:57:12PM +0200, Hartmut Goebel wrote:
> Am 16.09.2016 um 16:49 schrieb ng0:
> > 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.
>
> This is what the docs say about this;
>
> Sometimes it is more appropriate to separate the various types of files
> produced from a single source package into separate outputs. For
> instance, the GLib C library (used by GTK+ and related packages)
> installs more than 20 MiB of reference documentation as HTML pages.
> To *save space* for users who do not need it, the documentation goes
> to a
> separate output, called @code{doc}. [...]
>
> Some packages install programs with different ``dependency footprints''.
> […] This allows users
> who do not need the GUIs to *save space*. […]
>
> For me this sound more like a bug. But maybe someone can explain this.
Whether it's a bug or not, it sounds like the situation could be
improved. Can you file a bug report?
prev parent reply other threads:[~2016-09-24 0:33 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
2016-09-16 14:57 ` Hartmut Goebel
2016-09-24 0:32 ` Leo Famulari [this message]
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=20160924003259.GB24812@jasmine \
--to=leo@famulari.name \
--cc=h.goebel@crazy-compilers.com \
--cc=help-guix@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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.