Common code into source/ or toplevel? (Re: Suggested "combined tree" conditions for success)

[simo]

On Mon, 2008-09-15 at 10:13 +0200, Stefan (metze) Metzmacher wrote:
> Kai Blin schrieb:
> > On Monday 15 September 2008 09:25:53 Stefan (metze) Metzmacher wrote:
> > 
> >> I'd propose to move them to source/, to that all 3 ways of building
> >> code in the master branch have the same weight. I assume have the magic
> >> of the combined build in the top level directory would give more weight
> >> to the most experimental way of building samba.
> > 
> > Hm, I actually liked the idea of being able to build from the top dir, instead 
> > of having to cd into the source/ dir. We could get started on moving the 
> > tests from the various test dirs closer to the code they test and clean up 
> > there as well if clutter in the root dir is an issue.
> > 
> > My proposal is to have a Makefile in the root dir and have that build s3 
> > on "make samba3", s4 on "make samba4" and franky on "make franky". I'm open 
> > for suggestions on what should fall out of the tree on a plain "make". :)
> 
> Having a simple Makefile in the root dir is easy,
> but what about autogen.sh, configure.ac, VERSION?

Keep them in each subsytsem?

I Frankly would like to see less magic with makefiles and just build
each separate piece separately.

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer <simo at samba.org>
Senior Software Engineer at Red Hat Inc. <simo at redhat.com>