Mike Corbeil wrote:
> [snipped]
>
> > Well, if you *only* do --nodeps that's probably true, but if you use
> > --force you can get in trouble: the un-install could un-install stuff
> > that was really installed already.
>
> un-install usually means removing stuff that was already installed, as far
> as I'm aware.However, guessing, --nodeps could also cause problems.
> According to the aforementioned referenced documentation, --nodeps can
> install an app and this might work, but it can also cause other apps to be
> "broken", and I don't have any difficulty believe that this is definitely
> possible, and does happen.
Uninstall only un-installs what the package *thinks* it installed; once
you start messing around with the rpm options you can confuse this
process.
I have found that the best approach is to install/re-install individual
packages from hither & yon as infrequently as possible; unless you have
some specific reason to do so, stick to the packages that all came
together on your distribution.
I, at least, find it easier to just backup my system and re-install
periodically just to "keep up with what's new" and only install
piecemeal when I have a specific bug or problem.
>
> > You might try rpmdrake; it can resolve dependencies and install them all
> > automatically.
>
> Thanks for that point. Definitely sounds better than the rpm I'm currently
> using, 3.0.2. I've already found a couple of "bugs" with this version, one
> when erasing or removing 3.0.2 after it's been installed "next" to a prior
> version, and the other being that I now, somehow, have three instances of
> 3.0.2 reported with rpm -qa. Not sure how the latter happened, but
> definitely seems wrong.
rpmdrake is a GUI on top of RPM, not a replacement rpm.
In general packages don't install next to other packages, they replace
them.
I know of no reason why it wouldn't work with RH.
>
> On the other hand, the first bug is easy to recover from once one knows
> how, especially if there's another Linux configuration files and
> directories can be copied from, and the second bug doesn't prevent rpm from
> working; just that there are more instances reported by rpm -qa than
> necessary. Guessing, I believe that this may be more of a rpm database
> tracking error, but harmless.
>
> I'll take a look into rpmdrake, and believe it works for both Mandrake and
> RH.
>
> Screwed up my test/build system tonight doing configure, make and make
> install, for glibc2 2.x.x .tar.gz archive. Can't boot into that
> configuration any longer and now need to figure out how to undo or
> repair. That teaches me one lesson, to not install to /usr, but instead as
> the INSTALL file says to try first, to /usr/local.
I always install non-RPM code to /usr/local. Much safer.
>
> mike
--
"Brian, the man from babble-on" [EMAIL PROTECTED]
Brian T. Schellenberger http://www.babbleon.org
Support http://www.eff.org. Support decss
defendents.
Support http://www.programming-freedom.org. Boycott amazon.com.
