Re: Is missing SysV-init support a bug?
Philipp Kern <firstname.lastname@example.org> writes:
> On 2016-08-26 19:53, Wookey wrote:
>> After Stretch there may not be that many sysvinit users, but I think
>> that 2 releases is the minimum sensible period to maintain support for
>> such a siginificant change.
> But it seems that this discussion does not consider if sysvinit
> support in the conntrackd package is useful for the remaining sysvinit
> users or not. It seems to be more of a knee-jerk reaction to the
> removal, as in "we can't let that happen" because of some kind of
> assumed policy that hasn't been updated. It's one thing to assume
> precedent everywhere and let the maintainer actually determine what's
> the best for the package. Rather than users finding out the caveats
> mentioned in  the hard way by deploying the package on sysvinit.
If we assume that this precedent allow a maintainer to violate policy,
so we don't need the Policy anymore.
Does not matter if this package is useful for sysvinit users. Users are
maybe just not here. They may not even be developers. But they still
continue to rely on Policy to be sure that somebody takes care of their