[Kde-scm-interest] Package splitting

[Thiago Macieira]

Em Quinta-feira 28. Janeiro 2010, às 00.58.59, Oswald Buddenhagen escreveu:
> On Wed, Jan 27, 2010 at 10:46:52PM +0100, Thiago Macieira wrote:
> > [...] The build rules are: [...]
> 
> why not (mostly) keep our current layout in form of a meta structure (be
> it git submodules or not)? build order would be determined by cmakelists
> which declare subdirectories (and *nothing* else) as ever. breaking out
> of that layout would happen at own peril, but any breakage will be
> quickly detected anyway (as the projects' cmakelists must be
> self-contained and dependency-complete).

A Makefile is also a solution. Just put one in each "stage" (libs, release, 
review, playground) and declare the dependencies there.

I wouldn't do a CMakeLists.txt unless CMake is capable of completely isolating 
the subdirs. Because if we do truly independent repositories for each app, 
there will be conflicts in what is required by one and by another, variables 
being stepped over, etc.

> you know, sysvinit is now moving away from fixed priorities to a
> dependency-based system ... ;)
> anyway, my private build script does effectively the same, so it isn't
> that bad as such. :D

That's going away from my stated goals: dependencies resolved by humans.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20100128/fd1cfd41/attachment.sig