
Originally Posted by
helpme
I think the downsides are pretty clear.
1. The graphical frontends are frontends to apt, not aptitude, so if you manage your software from the command line and via synaptic and gnome-app-install you'll end up with a mixed environment, which is a mess.
I don't see how it's a mess. I use Synaptic, apt-get, and aptitude, and I've never run into any problems.
2. I never really tried aptitude, so correct me if I'm wrong, but from what I understand it's claim to fame is that it also gets rid of all the dependencies when you uninstall an application. Now this is of course great, however I'm not entirely sure if this isn't problematic when it comes to meta-packages. For example, if you want to get rid off something that ubuntu-desktop depends so this will lead to ubuntu-desktop being uninstalled. Now, couldn't there be the problem that when ubuntu-desktop and dependencies get uninstalled you'll get rid of a lot more software than you actually wanted to?
I'm not 100% sure, but I don't think that's the case. For example, in the link I posted above, here's an excerpt:
Code:
user@ubuntu:~$ sudo aptitude remove kword
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages are unused and will be REMOVED:
kspread libwv2-1c2
The following packages will be REMOVED:
kword
0 packages upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 19.6MB will be freed.
Do you want to continue? [Y/n/?] y
Writing extended state information... Done
(Reading database ... 80478 files and directories currently installed.)
Removing kword ...
Removing kspread ...
Removing libwv2-1c2 ...
user@ubuntu:~$
It's removing those dependencies because they're "unused." So my guess is that if they were... used... they would stay, but I haven't tested that theory yet.