From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [V2 2/2] graph-depends: add an option --stop-on-virtual
Date: Mon, 9 Mar 2015 21:15:08 +0100 [thread overview]
Message-ID: <20150309211508.39c2a0ac@free-electrons.com> (raw)
In-Reply-To: <CAB0FRsvxotGUKRC2q7R_JKPCajZb68X3r2qnjciehP-cqXENBg@mail.gmail.com>
Dear Fran?ois Perrad,
On Mon, 9 Mar 2015 20:32:16 +0100, Fran?ois Perrad wrote:
> I agree with you.
> The graphs become quickly too large.
> The current option --depth seems to be only a workaround against an
> infinite recursion when the graph has a cycle.
Well, I don't really think --depth is meant to avoid infinite
recursion: I don't think it's possible to have infinite recursion since
we can't have cyclic dependencies in Buildroot.
> But at this time, we haven't found the good way (or the good use
> cases) to limit the size of the graph.
I believe being able to exclude certain packages (and their dependency
tree) would be useful.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-09 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 14:29 [Buildroot] [V2 1/2] graph-depends: display virtual package with italic style Francois Perrad
2015-01-03 14:29 ` [Buildroot] [V2 2/2] graph-depends: add an option --stop-on-virtual Francois Perrad
2015-03-08 21:18 ` Thomas Petazzoni
2015-03-09 19:32 ` François Perrad
2015-03-09 20:15 ` Thomas Petazzoni [this message]
2015-03-14 16:26 ` Yann E. MORIN
2015-03-14 17:00 ` Thomas Petazzoni
2015-01-07 21:10 ` [Buildroot] [V2 1/2] graph-depends: display virtual package with italic style Yann E. MORIN
2015-03-02 16:20 ` Luca Ceresoli
2015-03-08 21:17 ` Thomas Petazzoni
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=20150309211508.39c2a0ac@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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