Nowadays apt supports deleting dangling config files with apt purge "~c" so no need to have aptitude for that feature. However, aptitude why <package> is pretty handy, and if you bump into dependency problems aptitude is quite capable of suggesting valid solutions.
I need to have aptitude because the TUI is boss. Even if it had less features than apt, I’d still prefer it. It’s nice to know it’s ahead of the curve, though.
Dude/dudesse, what the hell is this and why have I never heard of it? Sounds really useful on the manpage, I hope I remember it next time I need it. Thanks! 😊
Nowadays apt supports deleting dangling config files with
apt purge "~c"so no need to have aptitude for that feature. However,aptitude why <package>is pretty handy, and if you bump into dependency problems aptitude is quite capable of suggesting valid solutions.Disclaimer: I’ve never used aptitude’s TUI.
I need to have aptitude because the TUI is boss. Even if it had less features than apt, I’d still prefer it. It’s nice to know it’s ahead of the curve, though.
Dude/dudesse, what the hell is this and why have I never heard of it? Sounds really useful on the manpage, I hope I remember it next time I need it. Thanks! 😊