Tom Smith schreef: > Neil Bothwick wrote: > >> On Fri, 23 Dec 2005 02:16:52 +0000, Peter Ruskin wrote: >> >> >> >>> Well, of course! This is Gentoo - no rpm hell here! What you >>> need is "rpm -ivh --nodeps Win4Lin..." >>> >> >> >> Before you do that, check through the list of dependencies that rpm >> showed and make sure they are all installed. >> >> > That was my original question that started this thread... Which > Gentoo packages do I need to install to satisfy the dependencies that > RPM indicated were missing? That question has yet to be answered.
The RPM errors do not mean that those packages are not installed. I mean, come on-- > error: Failed dependencies: /bin/sh is needed by Win4LinPro-6.2.5-01 > ld-linux.so.2 is needed by Win4LinPro-6.2.5-01 libICE.so.6 is needed > by Win4LinPro-6.2.5-01 libSM.so.6 is needed by Win4LinPro-6.2.5-01 > libX11.so.6 is needed by Win4LinPro-6.2.5-01 libXext.so.6 is needed > by Win4LinPro-6.2.5-01 libXi.so.6 is needed by Win4LinPro-6.2.5-01 > libc.so.6 is needed by Win4LinPro-6.2.5-01 libcrypt.so.1 is needed by > Win4LinPro-6.2.5-01 libdl.so.2 is needed by Win4LinPro-6.2.5-01 > libgdk-1.2.so.0 is needed by Win4LinPro-6.2.5-01 libglib-1.2.so.0 is > needed by Win4LinPro-6.2.5-01 libgmodule-1.2.so.0 is needed by > Win4LinPro-6.2.5-01 libgtk-1.2.so.0 is needed by Win4LinPro-6.2.5-01 > libm.so.6 is needed by Win4LinPro-6.2.5-01 libnsl.so.1 is needed by > Win4LinPro-6.2.5-01 libpam.so.0 is needed by Win4LinPro-6.2.5-01 > libpthread.so.0 is needed by Win4LinPro-6.2.5-01 libutil.so.1 is > needed by Win4LinPro-6.2.5-01 libz.so.1 is needed by > Win4LinPro-6.2.5-01 libc.so.6(GLIBC_2.0) is needed by > Win4LinPro-6.2.5-01 libc.so.6(GLIBC_2.1) is needed by > Win4LinPro-6.2.5-01 libc.so.6(GLIBC_2.1.3) is needed by > Win4LinPro-6.2.5-01 libc.so.6(GLIBC_2.2) is needed by > Win4LinPro-6.2.5-01 libc.so.6(GLIBC_2.2.3) is needed by > Win4LinPro-6.2.5-01 libcrypt.so.1(GLIBC_2.0) is needed by > Win4LinPro-6.2.5-01 libdl.so.2(GLIBC_2.0) is needed by > Win4LinPro-6.2.5-01 libdl.so.2(GLIBC_2.1) is needed by > Win4LinPro-6.2.5-01 libm.so.6(GLIBC_2.0) is needed by > Win4LinPro-6.2.5-01 libm.so.6(GLIBC_2.1) is needed by > Win4LinPro-6.2.5-01 libnsl.so.1(GLIBC_2.0) is needed by > Win4LinPro-6.2.5-01 libpthread.so.0(GLIBC_2.0) is needed by > Win4LinPro-6.2.5-01 libpthread.so.0(GLIBC_2.1) is needed by > Win4LinPro-6.2.5-01 libpthread.so.0(GLIBC_2.2) is needed by > Win4LinPro-6.2.5-01 libutil.so.1(GLIBC_2.0) is needed by > Win4LinPro-6.2.5-01 Surely you don't think that you're missing /bin/sh or glibc!! The issue here is that RPMs use an RPM database to keep track of what is installed. You don't have an RPM database, because Gentoo is not a binary RPM-based distribution and therefore none of the dependencies were installed via RPM. You are never going to be able to convince the RPM which you're trying to install independently that the programs are already present. This is why --nodeps was suggested; the RPM you're trying to install won't then try to scan the non-existant database for programs that are installed, but not via RPM. Presumably the ebuilds for RPM applications do a complex process of linking the various aspects of the pre-compiled binary to the previously-existing aspects of the Gentoo system, so that the RPM doesn't freak out, and the Gentoo system can access the RPM program. Win4Lin is, naturally, a very complicated install, and so it's not as if you could just 'pop it in' as if it was Flash or the ATI drivers (one-function applications that don't require hooks to many parts of the base system). Were I you, I would consider looking at the most recent Win4Lin ebuild and see how it does it, then either try copying the ebuild to my overlay and updating it to work with the current version you have-- or as previously suggested, contacting the maintainer of the Win4Lin ebuild (or posting a bug to that effect) and seeing if you can get an update. After all, the maintainer will have to do this sometime, when the app is released, and perhaps it's a difficult procedure that takes some time. So it might be worthwhile to give said maintainer a heads-up now and get the ball rolling if it is not. At the very least, you might be able to get some tips as to how to get a provisional/temporary/overlay ebuild working, or what the issues involved might be. HTH, Holly -- gentoo-user@gentoo.org mailing list
