Subject: Re: Extreme lethargy when dependencies are missing (part 2)
To: <>
From: None <>
List: tech-pkg
Date: 10/08/2001 11:18:09
On Mon, 8 Oct 2001, Frederick Bruckman wrote:

> On Sun, 7 Oct 2001, Frederick Bruckman wrote:
> > On Sun, 7 Oct 2001 wrote:
> > > > can be listed as a dependency for a general ".DO_DEPENDS:" macro.
> > >
> > > so we'd pass down that WRKDIR to each child make?  I've been off and on
> > > thinking for quite some time about a good way to solve this problem once
> > > and for all.
> >
> > 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).