unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: guix-devel@gnu.org
Subject: Re: Guix size reduction work group
Date: Tue, 11 Feb 2020 15:20:28 +0100	[thread overview]
Message-ID: <87d0al2ok3.fsf@gnu.org> (raw)
In-Reply-To: <875zghdo7j.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Sat, 08 Feb 2020 17:43:28 +0100")

Hi,

Pierre Neidhardt <mail@ambrevar.xyz> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hi!
>>
>> Pierre Neidhardt <mail@ambrevar.xyz> skribis:
>>
>>> Shall we start a work group to fix the issue?
>>>
>>> - Write a blog article to explain the issue and a detailed process on
>>>   how to fix it.  (Embed it to the manual.)
>>
>> The “Submitting Patches” section mentions closure size specifically.  Is
>> there anything you think we should add there?
>
> It does not give much details, e.g. the ones that Julien mentioned.
> Also I don't think `guix size' is enough, see below.

‘guix size’ is a profiler, so when one is looking for ways to optimize
the size of package closures, it’s a good tool.

A graphical and interactive rendering would surely be an improvement,
but honestly, I don’t think that’s what’s preventing us from reducing
the size of our packages.  :-)

Thanks,
Ludo’.

      parent reply	other threads:[~2020-02-11 14:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 15:57 Guix size reduction work group Pierre Neidhardt
2020-02-04 16:22 ` zimoun
2020-02-04 17:59   ` Julien Lepiller
2020-02-05 15:18 ` Ludovic Courtès
2020-02-05 16:11   ` zimoun
2020-02-07 21:35     ` Ludovic Courtès
2020-02-07 22:31       ` Gábor Boskovits
2020-02-08 13:40         ` zimoun
2020-02-10 13:13       ` Tobias Geerinckx-Rice
2020-02-11 14:15         ` Ludovic Courtès
2020-02-08 16:43   ` Pierre Neidhardt
2020-02-09 23:45     ` zimoun
2020-02-10  8:09       ` Pierre Neidhardt
2020-02-10  8:46         ` Christopher Baines
2020-02-11 14:17           ` Ludovic Courtès
2020-02-10 10:30         ` zimoun
2020-02-10 12:33         ` Julien Lepiller
2020-02-11 14:20     ` Ludovic Courtès [this message]

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=87d0al2ok3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).