Since hal-0.5.10 hal-device-manager is no longer shipped, it is superseded by gnome-device-manager. So installing hal-device-manager with hal-0.5.10 results in broken symlink. I think that hal-device-manager should be blocked by >=hal-0.5.10.
Fixed the deps, and masked.
Why is it masked? It's perfectly valid for 0.5.9 HAL installations. gnome-device-manager isn't for 0.5.9 versions.
Yes, gnome-device-manager wants >=hal-0.5.10
I do not understand this, hal-device-manager works perfectly in hal-0.5.9, right? Currently I can't use anything like hal-device-manager while my system completely runs x86...
The thing is that gnome-extra/hal-device-manager package only contains symlink to hal-device-manager binary, installed by sys-apps/hal <= 0.5.9. Since hal-0.5.10 the source code of hal-device-manager no longer bundled. So installing gnome-extra/hal-device-manager along with hal-0.5.10 yields a broken symlink. hal-device-manager is now a separate project called gnome-device-manager. It's in the portage currently: gnome-extra/gnome-device-manager.
Okay so why don't you block hal-device-manager for HAL >=0.5.10 and gnome-device-manager for HAL <0.5.9? I don't understand why that's not possible.
it doesn't seem reasonable to mask a working code until we get the relevant hal versions out of the tree. Please unmask and fix this mess :)
Could someone please solve this problem? It's annoying to see portage complain about this non-issue every time. If the original dev disagrees it would be interesting to know why...
we don't need to be CCed here since we are in fdo already.
Mask message said: # Saleem Abdulrasool <compnerd@gentoo.org> (22 Jan 2008) # Never was stabled, and will not work with future versions of HAL. Remove when # HAL 0.5.10 is stabled on all arches. gnome-extra/hal-device-manager That was true, so treecleaners removed this package