[Juha Heinanen] > my conclusion is that the rules under which a package may list init > dependencies should be clarified by the debian people who have > invented the system.
I assume you mean init.d script dependencies, when you write "the system"? If so, it is part of the Linux Software Base, and not invented by Debian people. > in my opinion, the policy should be that init dependency of a > service on another service should only be listed if the init script > of the service cannot be run unless this other service is already > running ON THE SAME HOST. I believe this is already in place. There are two sets of dependencies, the required (required-*) ones and the optional ones (should-*). The optional ones only kick in if the two services in questions are installed on the same host. > on top of that, perhaps there could be a customization mechanism > that would allow system managers to add other init dependencies on > top of the default ones that obey the above stated rule. Already exist, by either editing the scripts directly or adding a file in /etc/insserv/overrides/. To me it seem like you are kicking in open doors. It still boils down to what the two maintainers want, ie which ordering they want by default for their packages scripts during boot. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
