Maybe an info message should be added to "libcdio-0.77.ebuild" that notifies the user to run "revdev-rebuild" (and to delete ~/.vlc/cache) after doing the update. Cheers, Axel
Does anyone know if this is usefull at all?
... it depends on what the gentoo policy is. Either inform the user about the fact that an update might break installed packages or trust the user to know that running revdep-rebuild is a good idea, if applications known to work do no longer work after an update. Cheers, Axel
As 0.77 is stable almost everywhere I think that such a message is not usefull. Please inform if 0.78.2 does break ABI/API, then we should add a message there.
This is a somewhat strange answer, I think ... So let's illustrate the problem with slighly more detail (but only for x86 arch) * latest x86-stable "vlc" is: 04 May 2006; Mark Loeser <halcy0n@gentoo.org> vlc-0.8.4a.ebuild: * Everybody who has build vlc (libcddax_plugin) before libcdio-0.77 became stable on x86 (2006-06-22) has linked against "libcdio.so.5" from "libcdio-0.73" * So updating "world" or "libcdio-0.77" after that time (2006-06-22) has affected ALL x86-stable builds of "vlc", because "libcdio.so.5" has been substituted by "libcdio.so.7". The problem persists until today and will NOT be solved by upddating to a newer version of libcdio. // NOTE: Updating from "libcdio-0.77" to "libcdio-0.78.2" is no // problem, because "libcdio.so.7" still exists after the update // (linked to libcdio.so.7.1.0) * The only way to get out of this situation to remerge "vlc" (and delete the per-user plugin cache) * ~x86 users of "vlc" might have noticed that the problem disappeared after running "update world" on 2006-07-04 (or later), because vlc-0.85-r4 became ~x86 in portage. I originally filed this BUG-Report, because I read a posting in the vlc forum (http://forum.videolan.org/viewtopic.php?t=22725&highlight=libcdio) In a nutshell: * Updating "libcdio" will NOT solve the problem * It's "vlc" or rather the vlc plugins that depend(s) on "libcdio" (and friends) that need(s) to be remerged (or updated) after updating from libcdio-0.73 to ANY newer version. And again, it's not up to me to decide whether users should be informed about the (known) fact that a library update breaks some (also known) packages. It's just that I've noticed that some gentoo developers do care about such things and add an einfo message ... :-) Axel
reopen for closing afterwards.
Added message to ebuilds 0.77 and 0.78.2.
