It's caused when the builder of the application has an NVidia video card and you don't .... I've had good luck with these by doing a nodeps install. This is I fear going to become an increasing problem as more and more builders have this card installed and since rpm has no way to say "ignore this dependency" I don't know a way around it. Like I've
Yes, there's a workaround developed by Buchan Milne but I don't have an URL right now.
said the program itself doesn't need this lib... but rpm building creates the dependency just because it's on the box of the builder.
But still I think it shouldn't. The package most probably doesn't depend directly on this library, it's a "second order" dependency (the package really depends on libGL.so.1, which normally is an XFree86 lib, but if it's been replaced by the Nvidia driver in turn depends on libGLcore.so.2 ie. package->libGL.so.1->libGLcore.so.2).
I don't know why rpm looks recursively at dependencies and doesn't stop at the first level (the second level should be taken care of by the package providing the first level dependency anyway).
Maybe some rpm guru can explain why things are done this way.
Bye
-- Luca Olivetti Note.- This message reached you today, it may not tomorrow if you are using MAPS or other RBL. They arbitrarily IP addresses not related in any way to spam, disrupting Internet connectivity. See http://slashdot.org/article.pl?sid=01/05/21/1944247 and http://theory.whirlycott.com/~phil/antispam/rbl-bad/rbl-bad.html
pgp00000.pgp
Description: PGP signature
