I don't want hal depending on acpid. I will patch the hal acpi addon to not
directly use the proc interface iff /usr/sbin/acpid exists.


The hal ACPI addon already won't directly use the proc interface iff /usr/sbin/acpid exists and acpid is started. The other case is /usr/sbin/acpid exists and acpid is not started. Apart from not directly using the proc interface, what will the hal ACPI addon do in this case? Abort hald's launch?

BTW, acpid is 180 kB and has no meaningful dependencies. This is a moderate size, even compared to hal itself. Is there anything other than acpid's size that makes you want to avoid depending on it?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to