Petter Reinholdtsen writes: > 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.
but, as i have mentioned earlier, even if two services are installed on the same host, one service does not need to use the other service on the same host, but on another 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/. thanks for the pointer. looks like it is good place to list "should-*" services in case system manager wants to use them on the same host. > It still boils down to what the two maintainers want, ie which > ordering they want by default for their packages scripts during boot. default should be that the packages are installable without a need to first configure something in /etc/insserv/overrides/. -- juha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
