[pkg-fso-maint] Upstart and sysvinit in packages - Policy needed

Marco Amadori marco.amadori at gmail.com
Mon Feb 14 19:59:53 UTC 2011

On Monday 14 February 2011 20:55:06 Tollef Fog Heen wrote:

> | I believe we need to come up with a way where most or all package
> | maintainers (perhaps those handling kernel events and early boot stuff
> | should be expected) only need to maintain one boot setup for their
> | package, and this boot setup should be used by all the different boot
> | systems.
> That would mean limiting each init system to the limitations of the most
> limited init system, which would be a sad state of affairs.  Also, I
> don't believe there's a 1:1 correspondence between the semantics of all
> the different init systems, making this a very hard if not impossible
> job.

I was about to replying exactly that, only not so well written :-)

In addiction to that, generally speaking, I was asking two things, one was if 
a policy could emerge to sort the init issues, the other point is regarding 
debhelper, maybe should I file a bug for the problem of debhelper hiding the 
sysvinit script if an upstart job is available?

I have some doubts because the two questions are related and it is not 
properly a bug, more a wanted design derived from an hint as it is now.


More information about the pkg-fso-maint mailing list