From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Installing headers to a separate output? Date: Sat, 27 Feb 2016 00:24:16 +0100 Message-ID: <87d1rjys0v.fsf@gnu.org> References: <87lh68fs4p.fsf@elephly.net> <20160225230533.3f4a69db@debian-netbook> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39776) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aZRkG-00041E-9l for guix-devel@gnu.org; Fri, 26 Feb 2016 18:24:25 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aZRkB-0002JW-Ky for guix-devel@gnu.org; Fri, 26 Feb 2016 18:24:24 -0500 In-Reply-To: <20160225230533.3f4a69db@debian-netbook> (Efraim Flashner's message of "Thu, 25 Feb 2016 23:05:33 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Efraim Flashner Cc: guix-devel@gnu.org Efraim Flashner skribis: > On Thu, 25 Feb 2016 21:32:22 +0100 > Ricardo Wurmus wrote: > >> Hi Guix, >>=20 >> 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. >>=20 >> Other distributions have separate =E2=80=9C*-devel=E2=80=9D or =E2=80=9C= *-dev=E2=80=9D packages (and I=E2=80=99m >> ambivalent about this) =E2=80=94 would it be a bad idea if we provided = =E2=80=9Cdevel=E2=80=9D >> or =E2=80=9Cdev=E2=80=9D *outputs* so that users had more control over w= hat ends up in >> their store? >>=20 >> I=E2=80=99m not writing this because I=E2=80=99m annoyed by the current = behaviour =E2=80=94 I=E2=80=99m >> just curious. >>=20 >> ~~ 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 =E2=80=9Cinclude=E2=80=9D output (there=E2= =80=99s 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=E2=80=99ve never seen a case wh= ere moving headers away would be a significant space saving. IOW, it=E2=80=99d be a micro-optimization; there are other things we could = do before that to save space. Ludo=E2=80=99.