Hi folks, One problem mentioned in a few bugreports is the handling of updates to /etc/default/rcS. Because it's not a conffile, we don't provide updates to it. While there are good reasons for this approach, I was thinking of ways of improving the situation.
While we don't want to lose any user customisation of this file, would it make sense to update the file to the latest version if it hasn't been modified? We can do this quite simply: take the sha1sum of the file, and compare it with a list of sha1sums of all the previous packaged versions of this file; if it matches, then it's not been modified, and so should be safe to upgrade. This would therefore mean all but the tiny minority of users who modify the file would then always have the current version and package defaults, and hence wouldn't be using the version from back when they originally installed their system. BTW, I started going through some of the open bugs and closing those fixed in current releases. Would there be any objection to reviewing and closing bugs which are no longer reproducible and/or which are no longer relevant on current systems? Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail. _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
