libdv installs a file called /usr/lib/libdv.so.4.0.0, then installs too two links for this file: libdv.so and libdv.so.2. But in the new version, media-libs/libdv-0.102), libdv.so.2 is renamed and now is called libdv.so.4. The problem is when you try to execute mplayer and you get an error and the program won't start. Reproducible: Always Steps to Reproduce: 1. ACCEPT_KEYWORDS="~x86" USE="encode" emerge mplayer 2. Test that the libdv version installed is libdv-0.102. 3. Try to execute mplayer. To resolve it: ln -s /usr/lib/libdv.so.4.0.0 /usr/lib/libdv.so.2
Remerge anything that depends on libdv including mplayer once you upgrade libdv. If you can show me that the two versions of libdv are binary compatible in all cases, then it would make sense to force an extra symlink in the ebuild.
I considered sloting this so that both version can exist at the same time, but for now, I'm just going to recommend remerging dependencies until libdv reaches 1.0 stable, and then see what the situation is at that time. For now, I'm closing this bug.
There should at least be some warning that this'll happen. While this may have not been a big issue when the bug was filed, libdv-0.102 was just recently moved from testing to stable, and that should imply that potential breakage like this either won't happen or is somehow automatically taken care of. Please consider re-opening, or re-masking libdv-0.102.
