unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Guix size reduction work group
Date: Tue, 11 Feb 2020 15:17:53 +0100	[thread overview]
Message-ID: <87k14t2ooe.fsf@gnu.org> (raw)
In-Reply-To: <87blq625jd.fsf@cbaines.net> (Christopher Baines's message of "Mon, 10 Feb 2020 08:46:46 +0000")

Hello!

Christopher Baines <mail@cbaines.net> skribis:

> I'm not quite sure how that would work, but the Guix Data Service can
> query for narinfo files, and from those it can store the size of
> specific outputs, as well as there references.
>
> So the closure size (I think?) is the size of an output, plus the
> closure size of all of its references (the definition is recursive).

Yes.  So the Data Service could pick that info from narinfo files and
have per-package pages with a graph showing the closure/self size
evolution—IOW, ‘guix size’ over time.

Doable, but easier said than done!

Ludo’.

  reply	other threads:[~2020-02-11 14:17 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 [this message]
2020-02-10 10:30         ` zimoun
2020-02-10 12:33         ` Julien Lepiller
2020-02-11 14:20     ` Ludovic Courtès

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