From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 02/02: gnu: next: Compress the executable.
Date: Mon, 16 Sep 2019 19:46:51 +0200 [thread overview]
Message-ID: <87y2yonng4.fsf@ambrevar.xyz> (raw)
In-Reply-To: <8736gw6xrh.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Same story: if the reference to ‘next-1.3.1-lib’ is invisible to the
> scanner or grafting code (due to compression, or due use of a non-ASCII
> compatible string encoding), the ‘next-1.3.1-lib’ might vanish.
But it's not, as shown in the first post by Ricardo.
next-1.3.1-lib is directly referenced by the asdf build system, there is
no risk for it to disappear.
So I'm still wondering how "guix size" could show dependencies that
could potentially be garbage-collected. Sorry if I'm missing the
obvious :p
Can we re-enable core compression for Next then?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-09-16 17:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190905095602.15524.75425@vcs0.savannah.gnu.org>
[not found] ` <20190905095603.AC57A209A5@vcs0.savannah.gnu.org>
2019-09-05 12:31 ` 02/02: gnu: next: Compress the executable Ricardo Wurmus
2019-09-05 12:51 ` Pierre Neidhardt
2019-09-08 21:19 ` Ludovic Courtès
2019-09-09 8:06 ` Pierre Neidhardt
2019-09-10 12:51 ` Pierre Neidhardt
2019-09-11 20:37 ` Ludovic Courtès
2019-09-12 9:49 ` Pierre Neidhardt
2019-09-16 15:56 ` Ludovic Courtès
2019-09-16 17:46 ` Pierre Neidhardt [this message]
2019-09-27 14:35 ` Pierre Neidhardt
2019-09-28 21:02 ` Ludovic Courtès
2019-09-29 7:59 ` Pierre Neidhardt
2019-09-29 13:24 ` Maxim Cournoyer
2019-09-29 13:43 ` Pierre Neidhardt
2019-10-02 7:53 ` Efraim Flashner
2019-10-02 13:27 ` Pierre Neidhardt
2019-10-02 15:01 ` Maxim Cournoyer
2019-10-02 15:20 ` Pierre Neidhardt
2019-10-02 15:59 ` btrfs and Guix features [was: gnu: next: Compress the executable.] Tobias Geerinckx-Rice
2019-10-02 16:31 ` Pierre Neidhardt
2019-10-02 17:48 ` Tobias Geerinckx-Rice
2019-10-02 18:59 ` Pierre Neidhardt
2019-10-08 4:41 ` Maxim Cournoyer
2019-10-08 7:44 ` Pierre Neidhardt
2019-10-09 1:58 ` Maxim Cournoyer
2019-10-03 7:09 ` 02/02: gnu: next: Compress the executable Efraim Flashner
2019-10-03 18:28 ` Bengt Richter
2019-10-04 8:08 ` Pierre Neidhardt
2019-10-08 7:05 ` Maxim Cournoyer
2019-10-08 7:48 ` Pierre Neidhardt
2019-10-09 1:50 ` Maxim Cournoyer
2019-10-09 8:05 ` Pierre Neidhardt
2020-02-27 15:38 ` Maxim Cournoyer
2020-02-27 15:48 ` Pierre Neidhardt
2020-03-03 5:14 ` Maxim Cournoyer
2020-03-03 9:43 ` Pierre Neidhardt
2020-03-11 2:09 ` Maxim Cournoyer
2020-03-26 8:38 ` Pierre Neidhardt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2yonng4.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.