From: zimoun <zimon.toutoune@gmail.com>
To: 28690@debbugs.gnu.org
Cc: rekado@elephly.net, post@thomasdanckaert.be, ludo@gnu.org,
dave.love@manchester.ac.uk, roel@gnu.org
Subject: [bug#28690] provide a lib output for boost
Date: Thu, 03 Feb 2022 03:30:00 +0100 [thread overview]
Message-ID: <86mtj81y3b.fsf_-_@gmail.com> (raw)
In-Reply-To: <86sftriqr3.fsf@gmail.com> (zimoun's message of "Thu, 13 Jan 2022 16:45:20 +0100")
Hi,
On Thu, 13 Jan 2022 at 16:45, zimoun <zimon.toutoune@gmail.com> wrote:
> This patch #28690 [1] is about adding an output to boost. The aim is to
> reduce the closure size.
>
> The last message if from Dec. 2017 and indicates some issues.
>
>
> 1: <http://issues.guix.gnu.org/issue/28690>
>
>
> On Tue, 03 Oct 2017 at 17:34, Dave Love <dave.love@manchester.ac.uk> wrote:
[...]
>> The lib package is 17MiB, and the headers are 108MiB.
>
> Now, the size is:
[...]
> total: 262.0 MiB
> On Mon, 04 Dec 2017 at 09:19, Thomas Danckaert <post@thomasdanckaert.be> wrote:
>> The updated list and a few patches are on my other computer, I'll post them
>> when I get home.
>
> Therefore, if I understand correctly, some work remains. The question
> is: is it worth to complete such work about adding more outputs to
> boost?
Since some work remains and it is not clear if it is worth to complete
such work about adding more outputs to boost, I plan to mark this report
as ’donewontfix’. Let me know if it is worth to keep it open.
Cheers,
simon
next prev parent reply other threads:[~2022-02-03 2:40 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
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 [this message]
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=86mtj81y3b.fsf_-_@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=28690@debbugs.gnu.org \
--cc=dave.love@manchester.ac.uk \
--cc=ludo@gnu.org \
--cc=post@thomasdanckaert.be \
--cc=rekado@elephly.net \
--cc=roel@gnu.org \
/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).