[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Installing headers to a separate output?
From: |
Ricardo Wurmus |
Subject: |
Installing headers to a separate output? |
Date: |
Thu, 25 Feb 2016 21:32:22 +0100 |
User-agent: |
mu4e 0.9.13; emacs 24.5.1 |
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
- Installing headers to a separate output?,
Ricardo Wurmus <=
- Re: Installing headers to a separate output?, Andreas Enge, 2016/02/25
- Re: Installing headers to a separate output?, Efraim Flashner, 2016/02/25
- Re: Installing headers to a separate output?, Ludovic Courtès, 2016/02/26
- Re: Installing headers to a separate output?, Ricardo Wurmus, 2016/02/27
- Re: Installing headers to a separate output?, Pjotr Prins, 2016/02/27
- git download size, Ricardo Wurmus, 2016/02/28
- Re: git download size, Ludovic Courtès, 2016/02/28
- Re: git download size, Pjotr Prins, 2016/02/28
- Re: git download size, Ludovic Courtès, 2016/02/28