all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dave Love <dave.love@manchester.ac.uk>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: 28690@debbugs.gnu.org
Subject: [bug#28690] provide a lib output for boost
Date: Fri, 20 Oct 2017 10:20:10 +0100	[thread overview]
Message-ID: <87tvyukwfp.fsf@albion.it.manchester.ac.uk> (raw)
In-Reply-To: <cuca80nxptb.fsf@thomasdanckaert.be> (Thomas Danckaert's message of "Thu, 19 Oct 2017 14:52:32 +0200")

Thomas Danckaert <post@thomasdanckaert.be> 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.

  reply	other threads:[~2017-10-20  9:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 16:34 [bug#28690] provide a lib output for boost Dave Love
2017-10-11  8:39 ` Roel Janssen
2017-10-19 10:57   ` Dave Love
2017-10-19 14:19     ` Roel Janssen
2017-10-20 12:58     ` Ludovic Courtès
2017-10-20 13:21       ` Thomas Danckaert
2017-10-20 16:14         ` Ludovic Courtès
2017-10-22 16:50           ` Dave Love
2017-10-22 19:03             ` Ludovic Courtès
2017-10-24 13:28               ` Thomas Danckaert
2017-10-24 15:30                 ` Ludovic Courtès
2017-12-03 23:07                 ` Ricardo Wurmus
2017-12-04  8:19                   ` Thomas Danckaert
2017-10-20 16:09       ` Dave Love
2017-10-20 20:14         ` Ludovic Courtès
2017-10-19 12:52 ` Thomas Danckaert
2017-10-20  9:20   ` Dave Love [this message]
2017-10-20  9:46     ` Thomas Danckaert
2017-10-20 15:34       ` Dave Love
2022-01-13 15:45 ` zimoun
2022-02-03  2:30   ` zimoun
2022-06-23 10:01     ` zimoun
2022-06-23 11:35       ` Thomas Danckaert via Guix-patches
2022-10-08 15:06         ` bug#28690: " zimoun

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=87tvyukwfp.fsf@albion.it.manchester.ac.uk \
    --to=dave.love@manchester.ac.uk \
    --cc=28690@debbugs.gnu.org \
    --cc=post@thomasdanckaert.be \
    /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.