From: Vincent Legoll <vincent.legoll@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: native or not
Date: Tue, 31 Mar 2020 11:51:57 +0200 [thread overview]
Message-ID: <CAEwRq=qD6mRiTQhQorDOr6dh=ngi0BHuqUns3+o7gOKwwWRnDQ@mail.gmail.com> (raw)
In-Reply-To: <87h7y4kgdq.fsf@nckx>
Hello,
On Tue, Mar 31, 2020 at 11:44 AM Tobias Geerinckx-Rice <me@tobias.gr> wrote:
> Vincent Legoll 写道：
> > I'm not seeing any size difference, but groff is not in the
> > output:
>
> There's some deeper confusion here: why do you expect the size to
> change, at all?
Because I've been told so...
On Mon, Mar 30, 2020 at 8:57 AM Mathieu Othacehe wrote:
> Well yes it may reduce the closure size of the package (run `guix size
> sudo`) to get it.
But I don't expect that to happen every time (I've seen the "it may")...
> Making ‘groff’ native was the right thing to do (and please, keep
> fixing bugs like this! :-) but it has nothing to do with making
> packages smaller.
Never will ?
I'm not expecting package size to shrink, but package closure
(is that the right word) size to sometimes shrink.
And if I've understood that may be visible for ISO, VM, container
image sizes.
Am I mistaken ?
Still learning...
--
Vincent Legoll
next prev parent reply other threads:[~2020-03-31 9:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 23:11 native or not Vincent Legoll
2020-03-30 6:57 ` Mathieu Othacehe
2020-03-30 21:25 ` Vincent Legoll
2020-03-30 22:07 ` Vincent Legoll
2020-03-31 7:45 ` Mathieu Othacehe
2020-03-31 8:02 ` Vincent Legoll
2020-03-31 9:17 ` Vincent Legoll
2020-03-31 17:54 ` Christopher Baines
2020-03-31 7:27 ` Mathieu Othacehe
2020-03-31 9:44 ` Tobias Geerinckx-Rice
2020-03-31 9:51 ` Vincent Legoll [this message]
2020-03-31 13:25 ` Marius Bakke
2020-03-31 22:01 ` Vincent Legoll
2020-03-31 22:04 ` [PATCH 1/6] gnu: cgit: Make some inputs native Vincent Legoll
2020-03-31 22:04 ` [PATCH 2/6] gnu: darktable: " Vincent Legoll
2020-04-01 13:58 ` Mathieu Othacehe
2020-04-01 14:15 ` Tobias Geerinckx-Rice
2020-03-31 22:04 ` [PATCH 3/6] gnu: graphviz: " Vincent Legoll
2020-03-31 22:04 ` [PATCH 4/6] gnu: iwd: " Vincent Legoll
2020-03-31 22:04 ` [PATCH 5/6] gnu: mailutils: " Vincent Legoll
2020-04-01 14:03 ` Mathieu Othacehe
2020-03-31 22:04 ` [PATCH 6/6] gnu: nethack: " Vincent Legoll
2020-04-01 14:06 ` Mathieu Othacehe
2020-03-31 23:07 ` [PATCH 1/6] gnu: cgit: " Tobias Geerinckx-Rice
2020-04-01 13:52 ` Mathieu Othacehe
2020-04-01 14:13 ` Tobias Geerinckx-Rice
2020-04-01 14:20 ` Mathieu Othacehe
2020-04-01 17:59 ` Vincent Legoll
2020-04-01 19:23 ` native or not Tobias Geerinckx-Rice
2020-04-01 21:28 ` Vincent Legoll
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='CAEwRq=qD6mRiTQhQorDOr6dh=ngi0BHuqUns3+o7gOKwwWRnDQ@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).