> On Thursday 08 September 2011 02:27:33 Timothy Pearson wrote: > >> > Can't you get the info You need from other sources? I mean sysfs, DBUS >> > and so on? >> >> Yes, but it's a pain. Additionally, as those interfaces change we would >> have to maintain the TDE connections to them, which would sap time and >> energy away from other tasks. >> >> I have not yet decided on a course of action, but probably nothing will >> be >> done as far as replacing HAL until either someone sponsors the work or >> does it themselves. > > I am currently writing from kdebase3 where hal has been disabled. > > Only the following packages need hal as of now and I placed them in a > separate repository: > > kima > knetworkmanager-kde3 > kpowersave > For Trinity, add kdebase and I end up with the same list, which is good. :-) Just as a reminder, I do have specifications out for the new libraries that Trinity should include when we do move away from HAL, in case anyone feels inspired to work on them: http://www.trinitydesktop.org/wiki/bin/view/Developers/TUComputerAPI http://www.trinitydesktop.org/wiki/bin/view/Developers/KPowerAPI A properly engineered base will prevent many problems down the line, and allow Trinity applications to easily access and control the computer's devices and power management state. Feedback on the proposed libraries is also welcome. Tim