On Wed, 24 Oct 2007, Eddy Petrișor wrote: > > I'm sorry, I don't see how triggers would help us here... care to explain? > > As I understand the purpose of acpi-support is to support and configure every > acpi enabled system that exists in an attepmt to make sure the current HW is > supported and acpi-support uses the appropriate scripts. > > Ok, suppose you leave the installation of the hw dependant packages to a third > party (say a tool which would be smart about what it installs via discover > information, or even d-i). So what is left for acpi-support to do is to be > interested about a trigger enabled by a package such as nvclock.
What for? We don't need to be informed that a package is installed. We just need to do the right thing when the user ask the computer to suspend itself. People keep inventing scenarios of improper usage of triggers. :) > I know the weak link of this approach is the magnificent tool that installs hw > spcific packages based on discover findings, but discover already includes a > script that can install packages based on those findings, I guess is necessary > to check how much more it needs to be expanded[1] and integrate it somehow in > the installation. Right, but all this is unrelated to triggers. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
