From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54754) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e5TUM-0005up-0C for guix-patches@gnu.org; Fri, 20 Oct 2017 05:21:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e5TUE-0003sf-AD for guix-patches@gnu.org; Fri, 20 Oct 2017 05:21:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:42423) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e5TUE-0003sO-6D for guix-patches@gnu.org; Fri, 20 Oct 2017 05:21:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e5TUD-00040G-T0 for guix-patches@gnu.org; Fri, 20 Oct 2017 05:21:01 -0400 Subject: [bug#28690] provide a lib output for boost Resent-Message-ID: From: Dave Love References: <87d164b36m.fsf@albion.it.manchester.ac.uk> Date: Fri, 20 Oct 2017 10:20:10 +0100 In-Reply-To: (Thomas Danckaert's message of "Thu, 19 Oct 2017 14:52:32 +0200") Message-ID: <87tvyukwfp.fsf@albion.it.manchester.ac.uk> MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Thomas Danckaert Cc: 28690@debbugs.gnu.org Thomas Danckaert writes: > I don't think it's possible to have one output of a package depend on > another, though. We could just add boost:lib to the inputs for every > package which relies on boost (except for packages which only rely on > header-only parts of boost)? Sorry, I don't understand; the usual problem seems to be _preventing_ that, e.g. to cure cycles. It may not be in the package definition, but if I mention "lib" in some file in "out", it will do the job, won't it? > Another solution might be to turn the 2 outputs into 2 separate guix > packages, "boost" and "boost-libs", where "boost" only contains the > headers, and has "boost-libs" as a propagated-input. I'm not sure if > this will do the right thing (i.e. make boost-libs available in the > build environment when boost is a regular input, but not propagate it > further), someone should try it out ;). > > Thomas I don't think that's necessary, but the fact that this sort of thing isn't straightforward seems to me a Guix deficiency which might be addressed.