[Cook] find the cookbook up the path? (fwd)

[Aryeh M. Friedman]

> Actually, the way that we did it was this:
> 
> .../top/Howto.cook
>        /libs/lib1/Howto.cook
>                  /src/*.c
>                  /hdr/*.h
>             /lib2/Howto.cook
>                  /src/*.c
>                  /hdr/*.h
>             /lib3/Howto.cook
>                  /src/*.c
>                  /hdr/*.h
>        /pgm1/Howto.cook
>             /src/*.c
>             /hdr/*.h
>        /pgm2/Howto.cook
>             /src/*.c
>             /hdr/*.h
> 
> The low level Howto.cook files set up the target for the proper
> directory and then sourced the top Howto.cook file.  The top Howto.cook
> file included all Howto.cook files below it.  Then the target was built.
>  That way, if you were in the pgm1/src directory (where there is no
> Howto.cook file) and you typed docook, it would properly build
> libs/lib1, libs/lib2, and pgm1 (since pgm1 depends on lib1 and lib2). 
> If you type docook in the top directory it would build all programs.

	There is a more elegant way using aliases but since we are currently
switching from FreeBSD to Linux (worst then NT if you ask me) I do not have
all the configs handy... once I recreate them I will post them (essencially
it is adding a few preprocessing commands to the docook alias).

	--Aryeh