Default PackageManager/ChangeSetSorter naive

[Anders F Björklund]

The default/basic implementation of PackageManager and ChangeSetSorter assumes that it can install/upgrade/remove packages one at a time. In practice, some packages with dependencies are required to be processed all at once or the operation will fail.

Currently there are special cases for deb and rpm to handle more complex transaction, but the other backends such as slack/arch/etc all use the naive approach and thus fail on transactions beyond the basic "install one, remove another" - for instance full upgrades.

It would be nice if more advanced code could be shared between the backends, so that the sorter could return groups of packages in the sorted package list. Then these groups of packages could be fed to the packagemanager and the transaction would succeed.

[Anders F Björklund (afb)]

This would be "when using the slack branch", since the slackware backend in trunk doesn't do dependencies (and thus doesn't see the problems either, until it tries the pm operation and fails).