From: ludo@gnu.org (Ludovic Courtès)
To: Dave Love <dave.love@manchester.ac.uk>
Cc: 28690@debbugs.gnu.org, Thomas Danckaert <post@thomasdanckaert.be>
Subject: [bug#28690] provide a lib output for boost
Date: Fri, 20 Oct 2017 22:14:26 +0200 [thread overview]
Message-ID: <87h8utd1b1.fsf@gnu.org> (raw)
In-Reply-To: <87wp3pkdh8.fsf@albion.it.manchester.ac.uk> (Dave Love's message of "Fri, 20 Oct 2017 17:09:39 +0100")
Dave Love <dave.love@manchester.ac.uk> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> The choice was made to allow package definitions to explicitly state
>> which outputs of their dependencies they’re interested in. So it you
>> have
>>
>> `("boost" ,boost)
>>
>> that’s only boost:out; if you have:
>>
>> `("boost" ,boost "lib")
>>
>> that’s only boost:lib. If you want both, you need to specify both.
>>
>> So far I don’t think this was considered a problem; on the contrary, you
>> could get fine-grain control, as in glib:out vs. glib:bin. In this
>> particular case, I agree that it’s annoying to have to specify both.
>>
>> If this “particular case” happens to be common enough, we can always
>> revisit the above decision and chance `("boost" ,boost) to mean “all the
>> outputs of boost.”
>
> It looks to me that it will be common if you want to reduce closures.
> Also, in other distributions you know that you can build-depend on the
> -dev(el) package and get what you need without having to know about
> various sub-packages (outputs), and the runtime requirements should be
> minimal (although there are sometimes problems with unnecessary
> dependencies). As far as I know, Guix doesn't have an easy way to find
> what provides particular files to determine the inputs.
Yeah, you may be right. Nixpkgs took that route when they introduced
multiple outputs not long ago.
Well, something to experiment with I guess!
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-10-20 20:15 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 [this message]
2017-10-19 12:52 ` Thomas Danckaert
2017-10-20 9:20 ` Dave Love
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8utd1b1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28690@debbugs.gnu.org \
--cc=dave.love@manchester.ac.uk \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).