Enrico Scholz <enrico.scholz <at> informatik.tu-chemnitz.de> writes:
afaik, smart splits transaction into sub-transactions so that e.g.
| install A-new
| install B-new ; B depends on A
| remove B-old
| remove A-old
| install C-new
| remove C-old
| install D-new
| remove D-new
sequences are possible. This does not remove possibility of dups
completely but reduces it significantly resp. the counts of dups.
Anaconda used to work like this too for upgrades (AFAIK, it even systematically
did install A, cleanup A etc. no matter what the dependencies were). Sadly this
has regressed to the much less failure-resilient "install all packages from a
CD/DVD/ISO, cleanup all installed packages" ordering with the switch to the yum
backend.
Kevin Kofler