>>>>> "DH" == Daniel Hartwig <[email protected]> writes: DH> [This experimental version has been withdrawn, I recommend you DH> downgrade to the latest in unstable.] Done. >> # aptitude -o APT::Install-Recommends=true install alsa-utils >> The following NEW packages will be installed: >> alsa-base{a} (R: alsa-utils) (for alsa-utils) alsa-utils >> # aptitude -o APT::Install-Recommends=true purge alsa-utils >> The following packages will be REMOVED: >> alsa-utils{p} >> >> Maybe it's because the two mutually recommend each other.
DH> Something like that. An empty install run should remove the cruft: DH> # aptitude install DH> otherwise it will likely be cleaned up during some subsequent operation. Didn't help. Anyway I'm sure the answer lies in the rest of what you wrote. However it's all getting too complicated for me. All I'm trying to say, is for that alsa pair, the concept of 'aptitude will take out the trash that older methods leave behind on your disk' is flawed... possibly due to the mutual recommends. I.e., on a virgin system # aptitude install alsa-utils # aptitude purge alsa-utils leaves cruft. _______________________________________________ Aptitude-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
