Emmanuel Bourg dixit: > Because separate packages means separate responsibilities. I'd like not
It’s a *TEAM* responsibility. I joined the team at some point in the past. > to maintain again sysvinit scripts in any Java package, we don't have > the time for this (we barely keep up with the Java and toolchain upgrades). I do have the time for this, because I feel it important, and I’ve offered about four or five times already to take care of it. > To avoid the proliferation of sysvinit script packages the best approach > would be to group the scripts into a common package (maybe using a trigger > to install the script when a supported daemon is installed on the system). This doesn’t scale, especially not to backports. There is an attempt to do so, but it’s only used for packages with overly hostile maintainers, and the approach doesn’t work flawlessly. I’m extremely unconvinced of this. > This would lift the burden of maintaining these scripts off most DDs and > delegate the work to a small set of dedicated maintainers, properly > optimizing and harmonizing these scripts. Why not let the dedicated maintainers take care of the scripts in their originating packages? Especially if they are part of the team that is listed as the package maintainer in the first place already ANYWAY? Exasperated, //mirabilos -- <hecker> cool ein Ada Lovelace Google-Doodle. aber zum 197. Geburtstag? Hätten die nicht noch 3 Jahre warten können? <mirabilos> bis dahin gibts google nicht mehr <hecker> ja, könnte man meinen. wahrscheinlich ist der angekündigte welt- untergang aus dem maya-kalender die globale abschaltung von google ☺ und darum müssen die die doodles vorher noch raushauen
