From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: 28690@debbugs.gnu.org, dave.love@manchester.ac.uk
Subject: [bug#28690] provide a lib output for boost
Date: Tue, 24 Oct 2017 08:30:08 -0700 [thread overview]
Message-ID: <87inf4pnr3.fsf@gnu.org> (raw)
In-Reply-To: <20171024.152840.126421535486070154.post@thomasdanckaert.be> (Thomas Danckaert's message of "Tue, 24 Oct 2017 15:28:40 +0200 (CEST)")
Thomas Danckaert <post@thomasdanckaert.be> skribis:
>>> I don't know if it helps, or is well-known anyhow, but you can
>>> check the
>>> dependencies of any that are in Debian by looking under
>>> https://packages.debian.org/sid/<package>.
>>
>> I don’t think it helps. I suggest looking for the direct
>> dependencies
>> of Boost in Guix, possibly using ‘guix refresh -l boost’.
>
> Doesn't that also lists indirect dependencies (575 of them)?
Yes it does.
> After some experimentation at the REPL, I came up with the following
> to find only packages directly depending on boost:
>
> (use-modules
> (srfi srfi-1)
> (guix packages)
> (gnu packages)
> (gnu packages boost)
> (guix scripts refresh))
>
> (define (depends-on-boost pkg)
> (any (lambda (p) (eq? p boost))
> (map cadr (append (package-inputs pkg)
> (package-propagated-inputs pkg)
> (package-native-inputs pkg)))))
>
> (let ((all-deps (filter depends-on-boost (fold-packages cons '()))))
> (format (current-output-port)
> "~{~a~^~%~}~%" (map package-name all-deps)))
>
> Leading to the 97 dependencies in the attached file.
Neat! We should add something like this to ‘guix refresh’.
> Is that approach correct? There are also 3 packages which have boost
> as a propagated input (mdds, gpgmepp and librevenge). That could lead
> to further packages depending on boost, which are missing from the
> list, but for now I'll assume that such cases are rare.
The approach looks correct, yes.
> Meanwhile I'll try to build those 97 packages, stay tuned ;-)
Awesome, let us know how it goes!
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-10-24 15:31 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 [this message]
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
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=87inf4pnr3.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).