Subject: Re: Extreme lethargy when dependencies are missing (part 2)
From: None <email@example.com>
Date: 10/09/2001 22:01:09
On Mon, 8 Oct 2001, Frederick Bruckman wrote:
> On Mon, 8 Oct 2001 firstname.lastname@example.org wrote:
> > > > Uh, no. You figure the depends once, before you do anything in the
> > > > DEPEND's directories, and then you do just the thing you need to do in
> > > > each DEPEND's directory (in reverse order). No need to recurse for
> > > > every target.
> > I guess I don't quite understand how the implementation would work. My
> > understanding is that the problem is, when a package like gnome has
> > several depends which each in turn depend on, for example gtk+, then when
> > we descend into each of those we in turn descent into gtk+ thus visiting
> > gtk+ multiple times. What we want to do is avoid visiting any particular
> > package more than once. What I don't quite understand is how/where the
> > list of visited packages is stored for access by various make processes.
> > I thought you were suggesting keeping this information in a file in the
> > top packages' WRKDIR
> > which is why I asked if this WRKDIR would be passed
> > down. So I'm missing something here (probably just me).
> There's nothing to pass down. For each (package,directory) in the
> top-level list, you'd change to it and run "make checksum" or "make
> no-recurse-check-install" or "make no-recurse-package", as applies.
I'm still confused then. Whats happens to the depends which are another
level down? Ie, gnome depends on gtk+ and gtk+ depends on glib.