On Wed, 24 Oct 2007, Eddy Petrișor wrote: > > What for? We don't need to be informed that a package is installed. We > > You would if acpi-suspend wouldn't blindly and needlessly depend on hw spcific > packages on systems where is not necessary.
Why would I need a dpkg trigger which is executed when nvclock is installed when I can do "test -x /usr/bin/nvclock" in my suspend script to know if the package is installed ? > Having nvclock installed as a consequence of a user choice of a system that is > able to detect and install that package on the systems that need it seems (to > me) like a nice and elegant way to enable different functionalities within > acpi-support. Yes, but triggers are not needed. > 3. scripts are no longer ran in a bundle on all systems, but instead a system > like it was proposed in #374734 is used; the symlinks are put in place via > triggers The cost of using the triggers outweighs largely the cost of adding an exit 0 at the start of a script if detects that nvclock is not installed. I mean I understand your suggestion but it's over-engineering... Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
