From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Keith Owens <kaos@ocs.com.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Janitor Project
<kernel-janitor-discuss@lists.sourceforge.net>
Subject: Re: [ANNOUNCE] include dependency graph script
Date: Sun, 30 Dec 2001 02:03:58 -0200 [thread overview]
Message-ID: <20011230020358.E2856@conectiva.com.br> (raw)
In-Reply-To: <20011230013033.A2856@conectiva.com.br> <23616.1009684530@ocs3.intra.ocs.com.au>
In-Reply-To: <23616.1009684530@ocs3.intra.ocs.com.au>
Em Sun, Dec 30, 2001 at 02:55:30PM +1100, Keith Owens escreveu:
> On Sun, 30 Dec 2001 01:30:33 -0200,
> Arnaldo Carvalho de Melo <acme@conectiva.com.br> wrote:
> > For the people that like me, Daniel Phillips and Manfred Spraul are
> >working on pruning the include dependencies in the kernel sources I made a
> >simple script to make a graphviz file to plot the dependencies in a nice
> >graphic, its available at:
> >
> >http://www.kernel.org/pub/linux/kernel/people/acme/hviz
>
> I suggest that you prune linux/config.h and autoconf.h from all graphs.
> The dependency system does not depend directly on those files, instead
> it depends on individual config options.
>
> It makes more sense to list the individual config options that an
> include file depends on, see the code in scripts/mkdep.c. Even then it
> would be better to suppress the config options by default and only list
> them when requested.
Thanks for the comments, this was a quick hack, I'll probably rewrite it in
python gleaning code from a tool we have here in Conectiva to prune/analise
the RPM packages dependency hell.
- Arnaldo
prev parent reply other threads:[~2001-12-30 4:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-30 3:30 [ANNOUNCE] include dependency graph script Arnaldo Carvalho de Melo
2001-12-30 3:55 ` Keith Owens
2001-12-30 4:03 ` Arnaldo Carvalho de Melo [this message]
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=20011230020358.E2856@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=kaos@ocs.com.au \
--cc=kernel-janitor-discuss@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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.
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.