> Whatever solution you create, just be careful how it slices up the
> tree.  The way 'make includes' is implemented now is somewhat silly,
> in that for 99% of the directories in the tree (i.e. everything but
> src/include, src/domestic/include, src/sys, and src/usr.bin/lex) it
> does nothing.

Quite honestly, i'd rather have a well-thought-out solution that runs
slowly than what we've got now.

I actually think 'make includes' is going in the right direction,
because it means that you can stuff a library/program/whatever that
installs a header just about anywhere in the tree, and it all works
out.

That actually makes sense for a bunch of things, e.g. ld.so's
"link.h", even though it's not necessarily done for them right now
since there has traditionally been no way to do it.



chris