[issue21] Prevent smart from downgrading when not necessary

[Tako Schotanus at Labix Tracker]

Tako Schotanus <quintesse at palacio-cristal.com> added the comment:

Ah, I didn't know a manually installed package could have a priority. How does
that work?

But even so, why downgrade _already_installed_ packages even if higher priority
versions exist? It just doesn't make sense to me and results in some very
undesirable behaviour when a repository can 't be reached or has problems. This
is not theoretical but happened to me some time ago when the kde-redhat
repository had some temporary package list problem: my entire KDE got
downgraded. In that particular case I could not even have upgraded other
packages without downgrading KDE or waiting until the problem got fixed. This
does not make smart very fool-proof and would require extensive system-knowledge
from the user performing the upgrade while I would rather just tell them to
blindly trust the upgarde always to work. (NB: smart already does a great job,
no mistake about that!)

I would think that to downgrade there must be something to upgrade that depends
on that older version, if not it should just be left alone.

_______________________________________
Labix issue tracker <tracker at labix.org>
<http://tracker.labix.org/issue21>
_______________________________________