All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [V2 2/2] graph-depends: add an option --stop-on-virtual
Date: Sat, 14 Mar 2015 17:26:57 +0100	[thread overview]
Message-ID: <20150314162657.GA4009@free.fr> (raw)
In-Reply-To: <20150309211508.39c2a0ac@free-electrons.com>

Thomas, Fran?ois, All,

On 2015-03-09 21:15 +0100, Thomas Petazzoni spake thusly:
> On Mon, 9 Mar 2015 20:32:16 +0100, Fran?ois Perrad wrote:
> > 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.

No, -depth was never meant to be a stop-gap for recursion: we can *not*
have recursive depedencies.

What I introduced --depth for, is because often only the first few level
of dependencies of a given package are of interest. --depth is
essentially meant for use when graphing the dependencies of a single
package, like so:

    BR2_GRAPH_DEPS_OPTS='--depth 2' make foo-graph-depends

that would limit graphinh the dependencies of 'foo' down to two levels.

> > 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.

What about something like:

    BR2_GRAPH_DEPS_OPTS='--stop-on PKGS' make graph-depends

where 'PKGS' would be a comma-separated list of packages, possibly a
glob or regexp, or even the keyword 'virtual' to stop on virtual
packages?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-03-14 16:26 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
2015-03-14 16:26         ` Yann E. MORIN [this message]
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=20150314162657.GA4009@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.