| 1 |
On Saturday 31 October 2009 22:36:34 Dale wrote: |
| 2 |
> Harry Putnam wrote: |
| 3 |
> > When I noticed the thread here about `hal' that started a while back |
| 4 |
> > it caused me enough curiousity that i ran eix -Ic ^hal$ but found I |
| 5 |
> > have no `hal' installed. |
| 6 |
> > |
| 7 |
> > I have keep up with updates somewhat better than usual the last few |
| 8 |
> > months but don't remember when hal went away... I do remember having |
| 9 |
> > some trouble with keyboard/mouse, and hal not starting, but that was |
| 10 |
> > quite a while back. |
| 11 |
> > |
| 12 |
> > I don't remember making a conscious effort to get rid of hal either. |
| 13 |
> > |
| 14 |
> > Evey thing seems to work ok here. I do notice a problem on bootup |
| 15 |
> > where the keyboard/mouse I have attached to a KVM does not become |
| 16 |
> > usable until AFTER the grub prompt. Somewhere between there and the |
| 17 |
> > appearance of the login prompt it becomes usable. But that has gone |
| 18 |
> > on at least a yr if not longer. |
| 19 |
> > |
| 20 |
> > So is there something wrong if I have no hal installed. Is it just |
| 21 |
> > not necessary or has it been replaced? |
| 22 |
> |
| 23 |
> I think it goes to show that a computer can work fine without hal. |
| 24 |
> Somebody nudge the KDE folks. Doesn't KDE require hal? |
| 25 |
|
| 26 |
There's no valid technical reason why an app *must* use hal. An app can try |
| 27 |
and do all hardware detection by itself, but it just makes more sense to use |
| 28 |
one common layer for that rather than every app doing essentially the same |
| 29 |
action. |
| 30 |
|
| 31 |
KDE-4 itself does not directly require hal. Solid does though: |
| 32 |
|
| 33 |
$ equery depends hal |
| 34 |
* Searching for hal ... |
| 35 |
app-emulation/wine-1.1.32 (hal ? sys-apps/hal) |
| 36 |
app-laptop/laptop-mode-tools-1.52 (hal ? sys-apps/hal) |
| 37 |
app-misc/hal-cups-utils-0.6.19 (>=sys-apps/hal-0.5.10) |
| 38 |
app-misc/hal-info-20090716 (>=sys-apps/hal-0.5.10) |
| 39 |
kde-base/solid-4.3.2 (>=sys-apps/hal-0.5.9) |
| 40 |
media-gfx/gimp-2.6.7 (hal ? sys-apps/hal) |
| 41 |
media-libs/libgphoto2-2.4.7 (hal ? >=sys-apps/hal-0.5) |
| 42 |
media-libs/libgpod-0.7.2 (hal ? =sys-apps/hal-0.5*) |
| 43 |
media-video/gxine-0.5.903 (hal ? sys-apps/hal) |
| 44 |
media-video/vlc-1.0.3_rc (hal ? sys-apps/hal) |
| 45 |
net-misc/networkmanager-0.7.1_p20090824 (>=sys-apps/hal-0.5.10) |
| 46 |
sys-apps/pcsc-lite-1.5.5 (hal ? sys-apps/hal) |
| 47 |
sys-power/pm-utils-1.2.5 (>=sys-apps/hal-0.5.10) |
| 48 |
x11-base/xorg-server-1.7.1 (hal ? sys-apps/hal) |
| 49 |
x11-drivers/xf86-input-synaptics-1.2.0 (hal ? sys-apps/hal) |
| 50 |
x11-libs/e_dbus-9999 (sys-apps/hal) |
| 51 |
|
| 52 |
There's nothing wrong with the *idea* of hal; it's the implementation of that |
| 53 |
app that makes it an utter piece of shit. It's called "feature-creep". |
| 54 |
|
| 55 |
Even it's author knows this (but apparently many distros do not) which is why |
| 56 |
he deprecated hal and started over with devicekit. |
| 57 |
|
| 58 |
|
| 59 |
-- |
| 60 |
alan dot mckinnon at gmail dot com |
Archives