Re: finding a dependency chain
----- Original Message -----
> From: "Kelly Clowers" <kelly.clowers@gmail.com>
>
> On Tue, Sep 2, 2014 at 1:44 PM, Rob Owens <rowens@ptd.net> wrote:
> > I'm trying to figure out, for example, what causes brasero to ultimately
> > depend on systemd. I found a utility called debtree, but it produces too
> > much output to be of use to me -- it shows all dependency chains starting
> > at brasero, but I am only interested in the one that ends at systemd.
> >
> > Can anybody suggest another utility, or maybe the proper syntax to make
> > debtree do what I want?
> >
> > Thanks
> >
> > -Rob
>
> I just used vim to search through debtree's .dot output (for such a
> complex thing, way easier than trying to look at the image file), and
> then followed up by looking around in aptitude interactive mode.
>
Thanks. That is much easier than looking at the image file!
I'd still like to find a method to specify the start point and end point, and get output of a single dependency chain. If anybody knows a way, please post it.
-Rob
Reply to: