Re: Upstart and sysvinit in packages - Policy needed
On Monday 14 February 2011 21:00:09 Olaf van der Spek wrote:
> On Mon, Feb 14, 2011 at 3:38 PM, Tollef Fog Heen <firstname.lastname@example.org> wrote:
> > ]] Petter Reinholdtsen
> > | 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
> Most isn't all. IMO there's way too much code duplication in current
> init scripts. Most daemons are pretty standard and shouldn't need any
> special code in their init script.
The problem is that they may, not that they should have different initscripts
for different init system.
The best of two worlds would be having a sane defaults for any initscript out
there from a common source but that a package maintainer could choose to
carefully write customized init script for the differents init systems.