From: ludo@gnu.org (Ludovic Courtès)
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: Installing headers to a separate output?
Date: Sat, 27 Feb 2016 00:24:16 +0100 [thread overview]
Message-ID: <87d1rjys0v.fsf@gnu.org> (raw)
In-Reply-To: <20160225230533.3f4a69db@debian-netbook> (Efraim Flashner's message of "Thu, 25 Feb 2016 23:05:33 +0200")
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Thu, 25 Feb 2016 21:32:22 +0100
> Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> Hi Guix,
>>
>> should we install headers to separate outputs as we do it in some cases
>> for really large documentation? It seems wrong to me to download
>> substitutes for libraries when at build time only certain headers are
>> needed.
>>
>> Other distributions have separate “*-devel” or “*-dev” packages (and I’m
>> ambivalent about this) — would it be a bad idea if we provided “devel”
>> or “dev” *outputs* so that users had more control over what ends up in
>> their store?
>>
>> I’m not writing this because I’m annoyed by the current behaviour — I’m
>> just curious.
>>
>> ~~ Ricardo
>
> I thought a bit about it before and I don't really think it'll save that much
> space. Most of the time the headers are a small part of the total package,
> and the fine-tuning that comes with chosing exactly which outputs from a
> build process you actually want seem like they should be left as
> encouragement for people to hack their systems.
Seconded. We can add a separate “include” output (there’s already a
special case for that in gnu-build-system) on a case-by-case basis, like
we do for documentation, but in practice, I’ve never seen a case where
moving headers away would be a significant space saving.
IOW, it’d be a micro-optimization; there are other things we could do
before that to save space.
Ludo’.
next prev parent reply other threads:[~2016-02-26 23:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 20:32 Installing headers to a separate output? Ricardo Wurmus
2016-02-25 20:40 ` Andreas Enge
2016-02-25 21:05 ` Efraim Flashner
2016-02-26 23:24 ` Ludovic Courtès [this message]
2016-02-27 11:33 ` Ricardo Wurmus
2016-02-27 19:40 ` Pjotr Prins
2016-02-28 9:48 ` git download size Ricardo Wurmus
2016-02-28 15:17 ` Ludovic Courtès
2016-02-28 15:46 ` Pjotr Prins
2016-02-28 15:45 ` Ludovic Courtès
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=87d1rjys0v.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@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.