On Mon, Aug 02, 2010 at 04:20:23PM +0300, Amit Kucheria wrote:
Separate source packages have the following features:
- One flavour of the kernel is not dependent on others
Dependent in what sense? There is some risk that with everything in one source package, a bug in a flavour-specific module will cause a build failure for all flavours; but I would expect this to stabilize fairly quickly, and we could always revisit the package organization if it proved to be an ongoing problem.
- Parallel builds (in theory, if there are build machines available)
- Different people can upload
- Different upload schedules
- More useful if we are going to carry non-upstream BSPs
Kernels that aren't built from the consolidated source tree are a separate issue. Certainly if it's built from a separate kernel tree, it needs to be a separate source package.
- More debian packaging overhead to deal with (debian developers might not
agree)
- Will go against kernel consolidation WG's work since we might end up with
one source tree per SoC
Again, a separate issue; if we build separate source packages for each flavour because it's convenient, those source packages should be strictly managed to avoid divergence between kernel source, with differences only in the package names, kernel configs, and module contents.
Single source package have the following features:
- Single source base for all kernels (multiple flavours to start with, but
single flavour once Kernel Consolidation WG is done with it)
- Long build times since builds are serialized
In the end, it depends on what exactly we want to package. Are we pushing all BSPs into a single source tree? Or are we carrying separate branches for each?
For me the only reason that could tip us in favor of separate source packages for a single kernel tree is the serialized build and long build time.
Cheers,