[9fans] Modularizing plan9port

[Enrico Weigelt <weigelt@metux.de>]

Hi folks,


I'm going to modularize plan9port a bit.

Ideally, each component (library, app, etc) should become it's
completely own package. This gets tricky because of the boostrapping
circle (mk requires lots libs, etc). In the current structure this
doesnt harm as mk is built directly with these libs' sources - but
an splitted tree won't this way.

So I intent do write some script which creates Makefile's from
mkfile's and maybe even does some build-time configuration
(sort of ./configure ;-)). That script(s) could be packet along
with some other fundamental p9p build utils, and this package
then would be the very first in depedency chain. Taking cross-
builds into account, this would be an TOOL or HOST dependency,
since it runs on the building host, not the target - an compiler-
less target wouldn't ever need it (it plays in the same liga as
tools like lex, make, autoconf, etc).

What do you think about this approach ?


cu
--
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 cellphone: +49 174 7066481   email: info@metux.de   skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------