On Tue, Apr 10, 2012 at 10:53 AM, Thomas Goirand <z...@debian.org> wrote: > Considering that most (if not all) scripts would be user custom-scripts, > I'd say that the best way would be to, just move them away on a special > folder, and execute them one by one, without any particular order, and > print a huge warning at boot time
With similar intention, I wondered about the possibility of running scripts without the LSB headers after everything else. (= implied dependency on those with LSB headers) Moving the broken scripts to another folder would be easy to implement, but doesn't integrate well with the packaging system -- some of these broken scripts may be from sysadmins' local packages, as well as from ancient packages that are still installed but no longer in Debian. (Detecting that and doing diversions wouldn't work either, as if a fixed version of a local package is installed, we don't want the fixed script to be diverted away.) However it's implemented, running non-LSB scripts after everything else clearly won't work in every case, but would solve the issue of obsolete-but-unpurged scripts harmlessly, and I expect would work for the majority of local scripts from sysadmins. The local scripts which will fail could already have been broken in the old scheme by package maintainers' changes to packaged scripts that they expected to run before -- there were no guarantees against the static ordering of packaged scripts changing. -- Moray -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cahwf6zpcy6c0lgy6mnbxxcip8i1jramn+nx8m-q+oz+tdpj...@mail.gmail.com