Tracing build dependencies

Jim Trigg jtrigg at
Tue Apr 27 16:17:23 PDT 2004

On Tue, Apr 27, 2004 at 06:53:13PM -0400, Randy Pratt wrote:
> On Tue, 27 Apr 2004 16:53:51 -0400
> Jim Trigg <jtrigg at> wrote:
> > > On Tuesday 27 April 2004 01:19 pm, Jim Trigg wrote:
> > > > I remember seeing come across one of the FreeBSD lists (either ports,
> > > > stable, or questions) a shell script to show build dependencies of
> > > > installed ports (for use in determining whether installed ports are
> > > > orphans or not), but cannot now find it (either in my saved mail, in
> > > > the list archives, or through a web search).  Does anyone have such a
> > > > script?
> I think you might be referring to a script I quickly wrote one day
> to use with pkg_cutleaves to find only build dependencies:

That was indeed the message I was looking for; thanks!  I don't know
why my googling on didn't find it...

> I rewrote that script after thinking about it a bit.  It had the
> drawbacks of having to have another database file and requiring it
> to be manually updated if you wanted it to reflect the current status
> of installed ports.
> If all you need to know is that something depends on a port, then
> this might do what you want.  It uses ports/INDEX as its source which
> includes both build and run dependencies.  No extra databases are
> needed but it makes no distinction whether its a build or run
> dependency.

Actually, what I really want is to supply the output of pkg_cutleaves -c
and have it tell me which of those ports is a build dependency for another
installed port.  I'm going to work on that, now that I have the basic

Jim Trigg, Lord High Everything Else  O-          /"\
                                                  \ /  ASCII RIBBON CAMPAIGN
Hostmaster, Huie Kin family website                X    HELP CURE HTML MAIL
Verger, All Saints Church - Sharon Chapel         / \

More information about the freebsd-ports mailing list