all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: guix-devel@gnu.org
Subject: Installing headers to a separate output?
Date: Thu, 25 Feb 2016 21:32:22 +0100	[thread overview]
Message-ID: <87lh68fs4p.fsf@elephly.net> (raw)

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

             reply	other threads:[~2016-02-25 20:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 20:32 Ricardo Wurmus [this message]
2016-02-25 20:40 ` Installing headers to a separate output? 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
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=87lh68fs4p.fsf@elephly.net \
    --to=rekado@elephly.net \
    --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.