I prefer
Submitted by root
| aptitude |
![]() 17% | 281 votes |
| apt-get |
![]() 59% | 937 votes |
| dpkg |
![]() 0% | 12 votes |
| gnome-apt |
![]() 0% | 5 votes |
| synaptic |
![]() 14% | 228 votes |
| wajig |
![]() 0% | 12 votes |
| kpackage |
![]() 0% | 8 votes |
| dselect |
![]() 4% | 69 votes |
| Total 1572 votes |
Felipe Sateler
[ Parent ]
[ Send Message | View Steve's Scratchpad | View Weblogs ]
Added it now, I'd not previously heard of it.
Steve
-- Steve.org.uk
[ Parent ]
--
"It's Not Magic, It's Work"
Adam
[ Parent ]
It is a bit slower because of some extra checkings, but it is also a more powerfull dependency problem solver than apt-get (If that is even possible ;)).
[ Parent ]
[ Parent ]
apt-get (by way of "--print-uris") & apt-cache allow non-root usage.
but as i'm tracking testing, unstable, & experimental (and prioritised in that order by way of pinnings), "apt-cache show blah" can scroll a 25-line xterm a few times displaying 3 different package descriptions for 3 different versions of the package. i would like to run synaptic in this situation (and for the filtering capability), but i'm not going to run it as root just for that. and the fact that i can't install packages using apt-get while browsing packages using synaptic, because synaptic locks the apt data directory. synaptic should only lock when necessary.
so i refuse to use synaptic until it gets rid of its god-complex (insisting on being ran as root, and locking apt's data directory).
[ Parent ]
[ Parent ]
For example if it is a fast machine and has X, I go for synaptic. If it is a cron job I am thinking of, I go for apt-get etc.,
But in the poll, there is no way to choose more than one option. Would it be possible to add such a facility?
[ Parent ]
[ Send Message | View Steve's Scratchpad | View Weblogs ]
I think polls, by their nature, should only really support one choice.
I accept that some polls will leave some users wishing to make more than one choice - but that's kinda what the comments are for.
Steve
-- Steve.org.uk
[ Parent ]
[ Parent ]
[ Parent ]
[ Send Message | View Steve's Scratchpad | View Weblogs ]
Thus proving that I should never be allowed to create my own polls.
dselect should have been included. I'll add it now, but it's probably lost a bit of voting choice.
Steve
-- Steve.org.uk
[ Parent ]
[ Parent ]
[ Send Message | View todsah's Scratchpad ]
[root@jib]/home/todsah# aptitude install iptraf
Reading package lists... Done
Building dependency tree
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following packages are unused and will be REMOVED:
debhelper gettext html2text intltool-debian po-debconf
The following packages have been kept back:
adduser asclock asclock-themes bluez-utils console-common dgen discover1
[-- snip --]
xterm xutils xvfb zlib1g zlib1g-dev
The following NEW packages will be installed:
iptraf
0 packages upgraded, 1 newly installed, 5 to remove and 122 not upgraded.
I don't want it to remove anything (especially something that I do use) and I don't want to know what's being kept back each time I'm installing an application. Compare apt-get:
[root@jib]/home/todsah# apt-get install iptraf
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
iptraf
0 upgraded, 1 newly installed, 0 to remove and 123 not upgraded.
after which it proceedes with the downloading and installation of iptraf.
I can't find any options for aptitude to turn off the uninstalling of packages when I do an 'aptitude install' nor can I find an option to turn off the displaying of everything that's being kept back. It's annoying.
I like aptitude's ncurses graphical front-end though. It's somewhat better than dselect's, but probably still too cryptic for newbies. It takes a while to get used to and, when I recently installed Debian on my new laptop, I still had to fall back to dselect for package selection because I wasn't used to the way aptitude displays conflicts. Turns out that was probably due to the C++ ABI change Debian was going through at the time.
For now, I'm simply going to be using a combination of dpkg (installation of third-party packages), apt-get (mostly for the 'install' option), dselect (for handling complicated dependency conflicts) and aptitude (installation of large ammounts of unrelated packages and browsing the repositories for cool software). Each has its strengths and weaknesses.
PS: The poll option 'deselect' should probably be 'dselect'.
PPS: The Preview option when posting is somewhat borked. It inserts many BR tags into the editing textarea.
PPPS: Excellent site!
[ Parent ]
# aptitude install debhelpershould solve your removal problems with aptitude.
(not sure about this, but is consistent with aptitude's behavior on my system :)
aptitude actually records the packages you have explicitly installed against the ones that came on your system through a dependency. As you installed debhelper using apt-get, it's not recorded as an "explicitly requested package". As no "explicitly requested package" depends on it, in aptitude's view, it should be removed.
[ Parent ]
[ Send Message | View todsah's Scratchpad ]
[ Parent ]
see how broken that is. i rather a package tool not include a feature, than include a broken one.
even worse, my main system was installed two years ago when deselect was used during installation (yuck!), and when aptitude was to some degree buggy, so i used apt-get. how would aptitude handle all those packages that were installed outside of itself, where it doesn't know if the package was installed explicitly or implicitly?
to solve my specific problem of unwanted/unused packages i use deborphan (and elaborate upon its output with a python script). a cron job runs deborphan once a day, i compare its output to a previous day's output to see what has recently been orphaned, and if it's something i don't want, i uninstall it. my cron job considers recommendations and suggestions the same as dependencies, but if i want to see those i just run deborphan again (discounting recommendations & suggestions) and compare/diff the output to that day's output.
i do this exercise every so often when i want to free up space on my /usr partition to find out what packages are candidates for uninstallation. yeah, it's a manual process (apart from the cron job), but it's always correct. ;-)
[ Parent ]
I seem to remember that you can toggle packages as Automatic using the 'a' (maybe it's 'A') key.
IIRC if a package is marked as automatic then it will be removed if nothing else is dependant on it. Although I do belive there is an option under one of the menus to disable this behaviour.
Perhaps this might help?
Laurence
(I'll try to remember to check my facts when I get home)
[ Parent ]
[ Parent ]
The name is a bit of a misnomer, it's actually a front end to dpkg-and-friends, apt-get, apt-cache, apt-file, debfoster, deborphan, dselect etc. It presents debian package management which is embarassingly and illogically spread out across a host of interface-inconsistent tools as a single user experience. Morover, it includes integrated help, and optionally (on by default) will show you how it is accomplishing all the tasks you ask of it, so you can learn all the Debian arcana if that sort of thing interests you.
Adding feta to my system made debian package management go from featureful but annoying to basically painless.
-- Joshua Rodman
[ Parent ]
[ Parent ]

17%