Mailinglist Archive: opensuse-es (614 mails)

< Previous Next >
[opensuse-es] Re: HAL [Era: KSynaptics OS11.2]
  • From: Camaleón <noelamac@xxxxxxxxx>
  • Date: Fri, 23 Apr 2010 07:01:54 +0000 (UTC)
  • Message-id: <pan.2010.04.23.07.01.53@xxxxxxxxx>
El Thu, 22 Apr 2010 23:02:22 +0200, Carlos E. R. escribió:

(...)

Dice Marcus Meissner en factory
Subject: Re: [opensuse-factory] What is the plan for HAL in 11.3 - HAL
or What?

What's the current line of thinking for 11.3?

I am not really seeing securitye flaws, but upstream decided that HAL is
not flexible enough nor exactly matching what they want so there was
redesign and it is being replaced by udev, udisks, upower,
media-player-db etc.


Y Lubos Lunak (KDE developer):

There doesn't seem to be a viable HAL alternative for KDE in 11.3, so
HAL is
needed for the time being.

Antes de eso dice:

"I assume the plan is to do whatever the decision of upstream is."

Y la decisión "upstream" es eliminarlo paulatinamente, manteniendo la
compatibilidad en las versiones antiguas de Xorg (<1.8):

***
http://www.x.org/wiki/XorgHAL

"(...)

Versions that do not use HAL

Since the HAL project has stopped development and deprecated itself,
X.Org is planning to move off HAL in the future. Support for udev instead
of HAL is available in X Servers 1.8 and later and enabled by default,
pending platform availability. As HAL was also used for input device
configuration, a new feature has been added to X Server 1.8 to support
configuration snippets in the xorg.conf.d directory. Instead of udev
rules, users and distributions are encouraged to use the xorg.conf.d for
configuration. Old-style xorg.conf configuration is still available."

O sea, que en la 11.3 sigue, pero lo van a quitar. O lo que es peor,
puede que parte del sistema lo use y parte no.

Quizá el uso de HAL sólo afecte a KDE...

Saludos,

--
Camaleón

--
Para dar de baja la suscripción, mande un mensaje a:
opensuse-es+unsubscribe@xxxxxxxxxxxx
Para obtener el resto de direcciones-comando, mande
un mensaje a:
opensuse-es+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups