From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Installing headers to a separate output?
Date: Sat, 27 Feb 2016 20:40:19 +0100 [thread overview]
Message-ID: <20160227194019.GA26683@thebird.nl> (raw)
In-Reply-To: <87lh66e6bs.fsf@elephly.net>
On Sat, Feb 27, 2016 at 12:33:11PM +0100, Ricardo Wurmus wrote:
> >> 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.
>
> Thank you all for your comments. I agree that it makes sense to do this
> on a case-by-case basis only.
>
> Curiosity: satisfied :)
Can we make the git binary download smaller? I think it is one of the
largest ones now in Guix. Since git is a small tool it really
shouldn't be that large despite that Linus was involved and some
people say it may be a larger contribution for posterity than the
kernel ;)
Pj.
next prev parent reply other threads:[~2016-02-27 19:41 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
2016-02-27 11:33 ` Ricardo Wurmus
2016-02-27 19:40 ` Pjotr Prins [this message]
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=20160227194019.GA26683@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.