Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#23756 - xfdesktop doesn`t list libnotify as deps but loads libnotify.so.1
Attached to Project:
Arch Linux
Opened by Leo (levantis) - Wednesday, 13 April 2011, 21:00 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 14 April 2011, 19:44 GMT
Opened by Leo (levantis) - Wednesday, 13 April 2011, 21:00 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 14 April 2011, 19:44 GMT
|
DetailsDescription:
After libnotify update, a lot of packages were broken because they needed libnotify.so.1 Having found packages that depend on libnotify and updated them all, the problem was resolved. However, xfdesktop still crashed becaused it wasn`t updated - it doesn`t list libnotify as its dependencies. The cure would be to make sure xfdesktop uses libnotify and put it in the dependencies. |
This task depends upon
xfdesktop already have libnotify as dependency from thunar
xfdesktop->thunar->libnotify
"xfdesktop already have libnotify as dependency from thunar
xfdesktop->thunar->libnotify"
I believe this way of reasoning is wrong.
a) Let`s say in the future, an alternative to thunar is made which doesn`t use libnotify. I remove thunar, libnotify (because thunar was the only package requiring it) and xfdesktop is left without it`s dependency. To resolve such situations, the package maintainer needs to check all xfdesktop`s dependencies dependencies, and then filter out which of them are still actual. I can count the expected number of deps needed to be checked, if you wish, but I believe this approach takes MUCH more time.
b) Let`s say thunar remains as the main and only FM for xfce, but migrates from libnotify to an alternative (quite a likely scenario, actually - remember OSS and ALSA?), so that it is no longer required. To check for such incidents, the maintainer would need to check all packages that require (directly OR indirectly) Thunar, and check each one for depending on libnotify. The situation is almost the same.
Of course, such incidents should have already been anticipated in the Arch Linux packaging policy, but I couldn`t find it. Are there any other arguments except trying to keep the dependency list minimal?