Re: [trinity-devel] Package renames and autoremove

On Wed December 10 2014 20:03:33 Michele Calgaro wrote: I would not recommend either apt-get or aptitude over the other as one is worse in some cases and the other is worse in other cases. Aptitude is maybe a bit smarter than apt-get and tends to autoremove automatically which is a separate step with apt-get. With a without-recommends standard install of 3.5.13.2 upgrade to R14 R2 aptitude avoids the conflict mentioned in bug 2245 because aptitude autoremoves kdebase-kio-plugins-trinity during the dist-upgrade, along with autoremoving roughly 47 other packages that would be a separate step with apt-get. When you try to purge the remaining roughly 15 dummy packages with aptitude it is smart enough to figure out on its own that kde-trinity and kde-core-trinity need to be removed ... but then you're in the same position as with apt-get - most of Trinity is autoremoved. // The above considered only a standard install. Let's now compare apt-get versus aptitude in the case of a small 3.5.13.2 install of just "kdm-trinity kdevelop-trinity" along with their depends but not their recommends. With apt-get after the dist-upgrade some but not all of the dummy packages are amenable to autoremove. Purging the remaining dummy packages results in the entire Trinity install becoming autoremovable. With aptitude the dist-upgrade proceeds as with apt-get except most of the dummy packages are autoremoved during the dist-upgrade. The only two remaining dummy packages are kdm-trinity and kdevelop-trinity. When aptitude is told to purge these two the entire Trinity install is autoremoved. // My guess is that the transition packages should somehow transfer their manual/auto state to the new packages but I don't know a clean way of doing this. --Mike