On Tue, 14 Nov 2000, Matthew Micene wrote: > On Tuesday 14 November 2000 03:02, you wrote: > > > > Trying to avoid --nodeps?? Never, never, never use nodeps is the > > fundamental rule with rpm's. > > And one of my biggest problems with the rpm system. If you compile > utilities and libraries from source, the rpm database has no idea they are > there, and will therefore fail rpms with dependency problems that do not > exist. I have and will continue to use the --nodeps option, but only in > cases where I am quite certain that rpm is wrong. You have another option, which is to create an rpm that will satisfy this dependency. It can be a dummy rpm, that simply decalres itself as supplying those rpms, but that does not seem any better than --nodeps. However, you can compile the library as a source rpm, create an rpm, and install it on your system. It takes longer to compile (you have to rebuild it all over again for every sungle change), and it takes some time to figure how to do this (the best way to start is to take an existing srpm of that library. or of another library of your distro). See: http://www.linux-mandrake.com/en/frpmapps.php3 The Maximum RPM book is also availble on-line. On the long run this makes a more organized system. rpm -q and rpm -V are really powerful tools. -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
