[ATrpms-devel] myth development sanction regular trunk rpm => merging myth and plugins?

[Axel Thimm]

Hi,

I've been asked to regularily offer trunk packages in a designated
area (e.g. the bleeding section). The packages are also to always be
built with full debug settings.

In order to do this one must be careful to not mix regular and trunk
builds and having mythtv+plugins split in two builds may pick up the
wrong packages.

The reason mythtv and mythplugins are separate packages are historical
(mythplugins was even several source tarballs once) and due to (some)
plugins having a different release cycle once, e.g. there could be
0.20.1 for some plugins and some + core would remain at 0.20. Having
them separate helped reducing the builds of the core package.

But since the advent of fixes branches the core package need to be
rebuilt each time just the same, so some of the reasons melt away, and
the new arguments for keeping it all under one src.rpm change the
balance.

So, what do you think? Merge mythtv and mythplugins into one build?
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20061109/02a0bc94/attachment.bin