That is not true about rpm if you compile from source. Its just a limitation of your knowledge about rpms. You can use the spec file to compile the source on your system and assemble it into an rpm so that you can install the new rpm on your system. Read up on building rpms and you will not have that limitation. Tom Berkley 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. It can be a dangerous > option if misused, but can be necessary at times. I would put it in the > expert user catagory of options, not one to ignore and pretend it was a > misfeature the developers left in. > > -- > Matthew Micene > Systems Development Manager > Express Search Inc. > www.ExpressSearch.com > ____________________________ > A host is a host from coast to coast, > and no one will talk to a host too close > Unless the host that isn't close is busy, hung or dead > > ------------------------------------------------------------------------ > Keep in touch with http://mandrakeforum.com: > Subscribe the "[EMAIL PROTECTED]" mailing list.
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
