7 Sep
2011
7 Sep
'11
11:51 p.m.
On Thursday 08 September 2011 03:43:08 Timothy Pearson wrote:
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. :-)
The most diappointing one here is the knetworkmanager client. In theory it should not
reqire hal?
and should only communicate with the NM backend.
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.