> @lct: If you run "apt-get autoremove", is hal uninstalled?

I can only *assume* it is *not*. 
I always use autoremove after upgrades (I upgrade via apt-get) and the 
situation with tons and tons of warning messages persisted up till now,
that is, until I explicitly checked for existing bug, 
tried to remove hal (synaptic) and hal-info,
no package disagreed,
no messages after boot up anymore.

But because I did not awarenessly issued autoremove *prior* to directly purging 
hal, I can't guarantee for that, but my assumption above about HAL's volatility 
and "injection" is very strong.

I did not believe it has to do anything with outdated HAL, nor I was aware of 
its presence in the system, because I thought that,
this was temporary issue due to switch or integration (as in "compatibility 
to") with systemd.

That said, I don't understand why would anyone still support the possibility to 
have HAL installed in current Debian Testing system.
It was deprecated from upstream, it was deprecated from current software stack, 
it is far less energy efficient, it is harder to configure and so on.

Thanks!

Reply via email to