The current dvgrab ebuild requires a "libdv.so.2" link to the current libdv.so.x.x.x. After you "ACCEPT_KEYWORDS='~x86' emerge -v kino", the dvgrab program stops due to a new dependent version of libdv ebuild being emerged as well.
Steps to Reproduce:
1. emerge dvgrab
2. ACCEPT_KEYWORDS='~x86' emerge -v kino
3. run dvgrab from command prompt.
dvgrab: error while loading shared libraries: libdv.so.2: cannot open shared
object file: No such file or directory
"": 0.00 MB 0 frames timecode 00:01:47.01 date 2004.07.13 17:32:38
Not sure if this is a kino ebuild issue, dvgrab ebuild issue, or a libdv ebuild
Yet another duplicate of bug 1991, it would seem.
This is what 'revdep-rebuild' is for.
Oh, and ACCEPT_KEYWORDS on the command line is evil.
Use /etc/portage/package.keywords instead.
What Peter said. This is unfortunately a limitation of portage, and why the revdep-rebuild tool exists. When in doubt, re-emerge the package that's giving you errors.
If you still have problems after another "emerge dvgrab" and/or revdep-rebuild, please reopen this bug.
*** This bug has been marked as a duplicate of 1991 ***