From: Roel Janssen <roel@gnu.org>
To: Dave Love <dave.love@manchester.ac.uk>
Cc: 28690@debbugs.gnu.org
Subject: [bug#28690] provide a lib output for boost
Date: Thu, 19 Oct 2017 16:19:43 +0200 [thread overview]
Message-ID: <874lqv9q4g.fsf@gnu.org> (raw)
In-Reply-To: <87shefmmm1.fsf@albion.it.manchester.ac.uk>
Dave Love writes:
> [Sorry, this got buried.]
>
> Roel Janssen <roel@gnu.org> writes:
>
>> Boost consists of various modules or components. Some of these are
>> "header-only". How does this patch handle that?
>
> The headers are in the main package, compatibly with the current
> situation if you're not doing anything which depends on the runtime.
>
>> If I were to install the "lib" output, could I then compile a C++
>> program that uses a header-only part of Boost?
>
> No. The point of the patch is not to pay the price of the headers in
> space at run time.
>
> I think you should be able to use just "boost" as an input, and build
> things which require the runtime (certainly for compatibility), hence my
> question about the right way to make the dependency.
>
> [I'm not convinced by Guix' convention for packaging compared with
> having the development sub-packages of other distributions, at least if
> you're trying to stop the closure of one package being comparable with
> the size I expect of an entire HPC node image.]
Ah, now I understand. We could indeed reduce the size of the closure
by having a small boost package that contains all the run-time
references needed by programs.
Thanks!
Kind regards,
Roel Janssen
next prev parent reply other threads:[~2017-10-19 14: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 [this message]
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
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=874lqv9q4g.fsf@gnu.org \
--to=roel@gnu.org \
--cc=28690@debbugs.gnu.org \
--cc=dave.love@manchester.ac.uk \
/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).