imacat <ima...@mail.imacat.idv.tw> wrote:
Well, up2date does not recognize the foreign RPM you downloaded from
the MySQL AB website. It only knows the so called "legal" RPMs from the
RPM repository server of your distribution. So, it has not idea that
the installing "lower-cased" "mysql" 4.1 conflicts with the existing
"MySQL" 5.0.
Funny, apt-rpm, smart, and yum all manage such a scenario. There's no
excuse for what up2date did, it was evil all the way.
The more stupid package managers (yes, yum) will say can't install X
because of conflict with Y. The 'smart'er ones will always try to let
you do what you ask, but give suitable warnings and ask for
appropriate confirmation.
Of course, up2date was never meant to be a proper package manager and
even Red Hat gave up on it as a POS.
Cheers,
Martin.
