On Tue, Jan 25, 2011 at 3:08 PM, Timothy Pearson
<kb9vqf@...> wrote:
>> By the way, how do you solve the problem of hal removal? I think we will
>> be in
>> necessity to add hal to our KDE3 repo once hal is removed from tha base
>> system.
>
> I'm working on a replacement using udev/upower.  It's a ways off though.

I don't know how hard this would be to do (I'm not quite there as far
as learning how to program, nor am I a hadware expert), but an idea I
came up with yesterday, haven't posted yet, is to replace calls to HAL
(or other hardware system) with a few lines of code that can allow for
plugging of a hardware system during compile. Also separate HAL from
the main code and make it pluggable to this system, as well as udev
and upower. Not all distros will use udev or HAL -- Ark is planning to
make an interim release with HAL and udev, and use a custom
replacement for HAL in the next release, we're just not using the
custom replacement because of problems with KDE4. The pluggable system
would make it easier to simply write libraries for Trinity for any new
project that may exist in the future for hotplugging hardware without
having to replace entire suggestions of code within KDE itself.
Hopefully that makes sense and won't be too much effort.

-- 
Kris
"Piki"
Ark Linux Webmaster
Trinity KDE Packager