On Fri, 02 Oct 2009, Paul Traina wrote: > Yes, amavis can depend upon a lot of stuff needing to start, so it > SHOULD start after those things, if they exist and are installed. > > The LSB stuff in /etc/init.d/amavisd-new should be tweaked or auto- > generated to fix this.
The only way we could autogenerate would be to have something the local admin can run, which will suggest changes to the LSB headers. That's way too much complexity for very, very little gain IMO. Anyway, the initscript is a conffile for a reason. The local admin is expected to edit it when necessary (and re-run insserv to reorder the boot, etc). And since the package is NOT going to use LDAP or SQL by default anyway, it can easily be argued that just documenting the need to edit the initscript (and give examples to make it easier, etc) would be enough. The alternative, which can be used only if the dep-based support is smart enough to let us depend conditionaly on, e.g., ldap and sql (as in: if any initscript provinding that exists, start after them) without causing trouble, would be to list by default the saner dependencies (LDAP, SQL). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
