On Friday 12 March 2010 12:42:11 you wrote: > From all the > available versions of a package, apt selects one upfront as the > candidate and then sticks with that. The only decision it makes is > between installing that candidate version, keeping the version you have > already installed, or removing the package altogether. It will not > reconsider which version should be the candidate based on dependencies > between packages.
I'm talking about a scenario when the application has an 'older than' dependency (often in combination with '|'), which apt (and HAM) *will* honour. So if app A has a libfoo << 2.0 dep, app B has libfoo >> 1.0, and there is currently a libfoo 1.5 in the repo, both A and B are installable. If you upload libfoo 2.5, however, and 1.5 gets automatically archived, app A is no longer installable (even though it could have been if you kept both versions of libfoo). Not a common case, I admit, just saying one has to be careful when removing packages from repos. Regards, Attila _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
