Only today I learned that there is widespread will to have both sysvinit
and upstart in meego 1.2.

I propose the following in order to accommodate both in trunk:

Create empty package "initprovider-meta" that would have Requires:
initprovider. Package groups would include initprovider-meta instead of
sysvinit as mic2 requires literal packages instead of fake ones (see
BMC#7499). Both sysvinit and upstart packages would have Provides:
initprovider so that mic2 would choose whichever has the highest
provided version, which would then be the default. By adding either
sysvinit or upstart to kickstart file would force mic2 to use
corresponding init provider.

I do not yet know how zypper reacts to updating system packages when
using the alternative init as there would be a possible upgrade of
initprovider meta package.

Deeper co-existence with both sysvinit and upstart on a single image
could be possible but would cause confusion among users and I don't
think that's worth it.

Filed as FEA#12715.


-- 
Tapio Rantala

_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to