From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Re: Guix size reduction work group
Date: Mon, 10 Feb 2020 07:33:11 -0500 [thread overview]
Message-ID: <EED6D97A-4235-4829-B05E-F877A70933F7@lepiller.eu> (raw)
In-Reply-To: <87r1z2c17u.fsf@ambrevar.xyz>
Le 10 février 2020 03:09:57 GMT-05:00, Pierre Neidhardt <mail@ambrevar.xyz> a écrit :
>zimoun <zimon.toutoune@gmail.com> writes:
>
>>> Say FOO has BAR in its closure, but not in the explicit inputs, how
>can
>>> I figure out which of the indirect inputs drags BAR in?
>>
>> I do not understand what you are looking for, but there is already:
>>
>> guix graph -t reverse-package
>> guix graph -t reverse-bag
>
>Yes, but this produces way too big a graph, which was my point below.
>
>> Maybe something more dynamic using 'd3.js' or similar to view *big*
>> graphs could help.
>
>Indeed!
>
>> The first step seems to list what operations and filtering is
>missing.
>
>I'm not sure what d3.js can do, but I can think of the following:
>
>- The ability to "hide" nodes and all their edges by making them
> translucent (so that they can be unhidden).
>
>- Hide/show all nodes inside the mouse rectangular selection.
>
>- Hide/show all nodes matching some text.
>
>- Close the current selection, that is, if some intermediary nodes are
> hidden for the currently showing nodes, show them.
>
>> You could propose such feature to the Guix Data Service.
>> For example, on this webpage [1], the history of all the Git package
>> in Guix is shown. The closure size could be reported.
>>
>> [1] http://data.guix.gnu.org/repository/1/branch/master/package/git
>
>This is a great idea! Christopher, what do you think?
I remember there was a script for graphviz floating around that could do exactly that: given two nodes it would only keep those in between them. Then you could generate a much smaller graph.
next prev parent reply other threads:[~2020-02-10 12:33 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 [this message]
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=EED6D97A-4235-4829-B05E-F877A70933F7@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@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).