From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] graphs: add option to remove transitive dependencies in dependency graph
Date: Fri, 09 May 2014 12:00:24 +0200 [thread overview]
Message-ID: <877g5vb7bb.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20140509095224.GB3173@free.fr> (Yann E. MORIN's message of "Fri, 9 May 2014 11:52:24 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi,
> All,
> On 2014-05-07 00:44 +0200, Yann E. MORIN spake thusly:
>> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
>>
>> Currently, all the dependencies of a package are drawn on the dependency
>> graph, including transitive dependencies (e.g. A->B->C and A->C).
>>
>> Very big graphs, with lots of packages with lots of dependencies, the
>> dependency graph can be very dense, and transitive dependencies are
>> cluttering the graph.
>>
>> In some cases, only getting the "build-order" dependencies is enough (e.g.
>> to see what impact a package rebuild would have).
>>
>> Add a new environment variable to disable drawing transitive dependencies.
> I've marked it as Changes Requested in PAtchwork, since I have a cleaner
> patch to come soon, with other cleanups in the graph-depends script.
Thanks. Like I mentioned on IRC I do like the looks of the graphs, but
I'm not really happy with the use of environment variables to control
it, as it isn't intuitive.
Perhaps we should simply have kconfig options for these things?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-05-09 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 22:44 [Buildroot] [PATCH] graphs: add option to remove transitive dependencies in dependency graph Yann E. MORIN
2014-05-09 9:52 ` Yann E. MORIN
2014-05-09 10:00 ` Peter Korsgaard [this message]
2014-05-09 10:20 ` Yann E. MORIN
2014-05-09 11:16 ` Samuel Martin
2014-05-09 13:34 ` Yann E. MORIN
2014-05-09 14:09 ` Samuel Martin
2014-05-09 14:38 ` Yann E. MORIN
2014-05-09 15:07 ` Samuel Martin
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=877g5vb7bb.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox