Re: switching from apt-get to aptitude
mustard lee [EMAIL PROTECTED] writes: One thing thats always confused me with aptitude is how to 'unmark' packages that I have accidently marked when uses the ncurses interface. You can use '-' (or '_') as Raquel suggested. Since this method requires that you look for the dependencies that were also marked, you might prefer C-u (undo), which will also unmark the dependencies. -- Bill Wohler [EMAIL PROTECTED] http://www.newt.com/wohler/ GnuPG ID:610BD9AD Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian! If you're passed on the right, you're in the wrong lane. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
Justin Guerin wrote: On Wednesday 17 May 2006 23:51, mustard lee wrote: Christopher Nelson wrote: On Wed, May 17, 2006 at 02:59:26PM +0200, H. Wilmer wrote: Florian Kulzer wrote: [snip] One thing thats always confused me with aptitude is how to 'unmark' packages that I have accidently marked when uses the ncurses interface. I have no trouble marking things and installing them, although, I generally use the command line for this. It usually when I have a lot of upgrades and I'd like to mark them all, and then unmark the few that I wannt to skip in upgrading, that I strike this problem of not knowing how to umark marked packages. Chris L. From /usr/share/doc/aptitude/README: ||Cancel any pending installation, upgrade, or | |Package-Keep (:) |removal of the currently selected package, and | ||remove any hold that was set on the package. | ||_| |Package-Hold (=) |Hold the currently selected package back.| ||_| If you previously put a hold on a package, : will remove it, but then again, if a package was on hold, choosing to upgrade them all should honor that. Note that sometimes, pressing : won't seem to have any effect. This is because another package you're choosing to install / upgrade conflicts with that package, and you'll need to cancel the pending operation on that package as well. If the conflict resolution dialog doesn't come up, then press g once to review the pending operations. The package you're wanting to hold should be in the list of packages to be removed due to unsatisfied dependencies. If you highlight that package, the information pane will tell you that another package conflicts with it, so it's being removed. You can then search for that package, cancel its pending operation, and unless there's another dependency, your original package will now be properly held back from the upgrade. After you change the preview (the tab you're in after you press g once), it will update, but I always use q to close that tab, then press g again to generate the preview again, so I'm sure no packages are listed in unexpected places. Naturally, if you choose to review carefully what packages will be removed, upgraded, or installed before pressing g again, you'll never be surprised at what aptitude does. This is why I never understood how people can have aptitude remove packages without them expecting it. Justin Thanks for the input. Chris L. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
Grant Thomas wrote: For example, a few days ago I decided to take a look at KDE (I am a long time IceWM user). I just did 'aptitude install kde' and had almost several hundred MB worth of k* applications. Exactly what I wanted and, so far, exactly what apt-get would have done. But it was just an experiment and I wanted to get rid of KDE again. Aptitude allowed me to just 'aptitude purge kde' again and it removed *every* package kde depended on. If I had used apt-get to install and remove kde, apt-get Even X? Of course not! But you are right, I should have made myself more clear: aptitude removed every package kde depended upon *that were not yet installed* when I requested installation of kde. Question for you (anyone) then: If you install kde through aptitude, an aptitude marks Xorg as a dependency, and then install gnome a couple of days later, would removing kde also remove Xorg, or would it see it as a current dependency for gnome and leave it? Once I installed a minimal Etch system, then used apt or aptitude to install Gnome (gnome-desktop-environment package). When I tried to start X, it failed. Why? Because I didn't install X! I don't think Xorg is a dependency of Gnome, KDE, or as far as I know, any other DE or WM. You have to explicitly install it. So using aptitude to remove any DE/WM won't remove Xorg. Doing aptitude show kde in Sid shows that the x-window-system-core package is a suggests, not a recommends or a depends. Also, in Sid, the new X server metapackage xorg does not install any WM, not even twm. The package description states It should be noted that a package providing x-window-manager should also be installed to ensure a comfortable X experience. -- Michael M. ++ Portland, OR ++ USA No live organism can continue for long to exist sanely under conditions of absolute reality; even larks and katydids are supposed, by some, to dream. --S. Jackson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
On Wed, May 17, 2006 at 02:59:26PM +0200, H. Wilmer wrote: Florian Kulzer wrote: You cannot break anything by using aptitude and apt-get together, but you will (partially) neutralize many of the advantages of aptitude. Just think of aptitude as a tool which integrates the functionality of apt-get, apt-cache, etc. into one utility with an optional ncurses-GUI and a broader repertoire for the resolution of dependency problems. Hm, I tried aptitude and found that you won't know what's going on anymore and that it tries to do things to packages you won't want it to do and that it's impossible to prevent that and very difficult, if not impossible, to make it install the packages you want. When using it after a fresh install, it appears to leave you with a totally broken system. In other words: Aptitude just utterly sucked, so I went back to dselect. This is exactly what I thought (althogh I never got along with dselect either) so I always went back to apt-get+debfoster. Recently debfoster was deprecated and I was more or less forced to take a look at aptitude. So far my experience is that it IS good, though it takes a little while to get used to it and figure out the UI. After getting some help from this very list I'm now using aptitude in a manner very similar to how I previously used apt-get+debfoster. I wrote some stuff down so that I would remember[1]. /M 1. http://therning.org/magnus/archives/132 -- Magnus Therning(OpenPGP: 0xAB4DFBA4) [EMAIL PROTECTED] http://therning.org/magnus Software is not manufactured, it is something you write and publish. Keep Europe free from software patents, we do not want censorship by patent law on written works. The definition of insanity is doing the same thing over and over again and expecting different results. -- Albert Einstein pgpuFV0tkvtkx.pgp Description: PGP signature
Re: switching from apt-get to aptitude
On 18 May 2006, Magnus Therning wrote: On Wed, May 17, 2006 at 02:59:26PM +0200, H. Wilmer wrote: Florian Kulzer wrote: You cannot break anything by using aptitude and apt-get together, but you will (partially) neutralize many of the advantages of aptitude. Just think of aptitude as a tool which integrates the functionality of apt-get, apt-cache, etc. into one utility with an optional ncurses-GUI and a broader repertoire for the resolution of dependency problems. Hm, I tried aptitude and found that you won't know what's going on anymore and that it tries to do things to packages you won't want it to do and that it's impossible to prevent that and very difficult, if not impossible, to make it install the packages you want. When using it after a fresh install, it appears to leave you with a totally broken system. In other words: Aptitude just utterly sucked, so I went back to dselect. This is exactly what I thought (althogh I never got along with dselect either) so I always went back to apt-get+debfoster. Recently debfoster was deprecated and I was more or less forced to take a look at aptitude. So far my experience is that it IS good, though it takes a little while to get used to it and figure out the UI. After getting some help from this very list I'm now using aptitude in a manner very similar to how I previously used apt-get+debfoster. I wrote some stuff down so that I would remember[1]. My experience with aptitude has also been pretty negative, with mass removal of wanted packages on more than one occasion. I'm surprised that no one has mentioned wajig, which I've found to be a brilliant way of integrating the functioning of the various packages. (Unfortunately there is currently an unresolved issue with the show command in wajig following a recent apt upgrade but otherwise wajig is still OK.) Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
Clive Menzies wrote: [ ... ] The problem with mixing aptitude with apt is that aptitude will sometimes threaten to remove packages it thinks are dependencies becuase it wasn't used to install [ ... ] This is because aptitude labels packages as either automatically installed or manually installed. If you have installed some packages using eg apt-get, you should be able to mark all installed packages as manually installed before using aptitude. The command from the man page is aptitude unmarkauto Unfortunately, I do not know which argument to supply. # aptitude unmarkauto * seems to look at every file in the current directory, not just packages. Has anyone got a solution? Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
On Thu, May 18, 2006 at 10:04:40AM +0100, Chris Lale wrote: Clive Menzies wrote: [ ... ] The problem with mixing aptitude with apt is that aptitude will sometimes threaten to remove packages it thinks are dependencies becuase it wasn't used to install [ ... ] This is because aptitude labels packages as either automatically installed or manually installed. If you have installed some packages using eg apt-get, you should be able to mark all installed packages as manually installed before using aptitude. The command from the man page is aptitude unmarkauto Unfortunately, I do not know which argument to supply. # aptitude unmarkauto * seems to look at every file in the current directory, not just packages. Has anyone got a solution? # aptitude unmarkauto --schedule-only '~i' Install aptitude-doc and take a look at file:///usr/share/doc/aptitude/html/en/ch02s03.html I personally want the bare minimum of packages to be installed 'unmarkauto'. Since I moved from debfoster to aptitude I had resonably short list of top-level packages (i.e. packages that aren't depends or recommends of another installed package). I started out with marking *all* packages auto and then toggling the packages on the list. Somehow that didn't quite do it, but I had shortened the list of packages to deal with manually to less than 10, definately doable. If you don't have that list there'll be more work to be done, but I'm sure that something clever can be done by limiting the package view. /M -- Magnus Therning(OpenPGP: 0xAB4DFBA4) [EMAIL PROTECTED] http://therning.org/magnus Software is not manufactured, it is something you write and publish. Keep Europe free from software patents, we do not want censorship by patent law on written works. And a government of the people, by the people and for the people will not enact laws that support DRM in any way. -- Richard M. Stallman on DCMA and DRM, ANU talk pgpo094YD1Ndq.pgp Description: PGP signature
Re: switching from apt-get to aptitude
On Thu, 18 May 2006 15:51:10 +1000 mustard lee [EMAIL PROTECTED] wrote: One thing thats always confused me with aptitude is how to 'unmark' packages that I have accidently marked when uses the ncurses interface. I have no trouble marking things and installing them, although, I generally use the command line for this. It usually when I have a lot of upgrades and I'd like to mark them all, and then unmark the few that I wannt to skip in upgrading, that I strike this problem of not knowing how to umark marked packages. Chris L. Use the - key to unmark a package scheduled for installation. Check the help. -- Raquel We are so accustomed to disguise ourselves to others that in the end we become disguised to ourselves. --Francois de la Rochefoucauld -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
On Wednesday 17 May 2006 23:51, mustard lee wrote: Christopher Nelson wrote: On Wed, May 17, 2006 at 02:59:26PM +0200, H. Wilmer wrote: Florian Kulzer wrote: [snip] One thing thats always confused me with aptitude is how to 'unmark' packages that I have accidently marked when uses the ncurses interface. I have no trouble marking things and installing them, although, I generally use the command line for this. It usually when I have a lot of upgrades and I'd like to mark them all, and then unmark the few that I wannt to skip in upgrading, that I strike this problem of not knowing how to umark marked packages. Chris L. From /usr/share/doc/aptitude/README: ||Cancel any pending installation, upgrade, or | |Package-Keep (:) |removal of the currently selected package, and | ||remove any hold that was set on the package. | ||_| |Package-Hold (=) |Hold the currently selected package back.| ||_| If you previously put a hold on a package, : will remove it, but then again, if a package was on hold, choosing to upgrade them all should honor that. Note that sometimes, pressing : won't seem to have any effect. This is because another package you're choosing to install / upgrade conflicts with that package, and you'll need to cancel the pending operation on that package as well. If the conflict resolution dialog doesn't come up, then press g once to review the pending operations. The package you're wanting to hold should be in the list of packages to be removed due to unsatisfied dependencies. If you highlight that package, the information pane will tell you that another package conflicts with it, so it's being removed. You can then search for that package, cancel its pending operation, and unless there's another dependency, your original package will now be properly held back from the upgrade. After you change the preview (the tab you're in after you press g once), it will update, but I always use q to close that tab, then press g again to generate the preview again, so I'm sure no packages are listed in unexpected places. Naturally, if you choose to review carefully what packages will be removed, upgraded, or installed before pressing g again, you'll never be surprised at what aptitude does. This is why I never understood how people can have aptitude remove packages without them expecting it. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
Magnus Therning wrote: [ ... ] # aptitude unmarkauto --schedule-only '~i' Install aptitude-doc and take a look at file:///usr/share/doc/aptitude/html/en/ch02s03.html [ ... ] Thanks, Magnus. Worked a treat. Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
Magnus Therning wrote: [ ... ] # aptitude unmarkauto --schedule-only '~i' Install aptitude-doc and take a look at file:///usr/share/doc/aptitude/html/en/ch02s03.html [ ... ] Thanks, Magnus. Worked a treat. Chris. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
Grant Thomas wrote: Question for you (anyone) then: If you install kde through aptitude, an aptitude marks Xorg as a dependency, and then install gnome a couple of days later, would removing kde also remove Xorg, or would it see it as a current dependency for gnome and leave it? It would see it as a dependency for gnome regards, Joris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
Florian Kulzer wrote: You cannot break anything by using aptitude and apt-get together, but you will (partially) neutralize many of the advantages of aptitude. Just think of aptitude as a tool which integrates the functionality of apt-get, apt-cache, etc. into one utility with an optional ncurses-GUI and a broader repertoire for the resolution of dependency problems. Hm, I tried aptitude and found that you won't know what's going on anymore and that it tries to do things to packages you won't want it to do and that it's impossible to prevent that and very difficult, if not impossible, to make it install the packages you want. When using it after a fresh install, it appears to leave you with a totally broken system. In other words: Aptitude just utterly sucked, so I went back to dselect. GH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
On Wed, 17 May 2006 14:59:26 +0200 H. Wilmer [EMAIL PROTECTED] wrote: Florian Kulzer wrote: You cannot break anything by using aptitude and apt-get together, but you will (partially) neutralize many of the advantages of aptitude. Just think of aptitude as a tool which integrates the functionality of apt-get, apt-cache, etc. into one utility with an optional ncurses-GUI and a broader repertoire for the resolution of dependency problems. Hm, I tried aptitude and found that you won't know what's going on anymore and that it tries to do things to packages you won't want it to do and that it's impossible to prevent that and very difficult, if not impossible, to make it install the packages you want. When using it after a fresh install, it appears to leave you with a totally broken system. In other words: Aptitude just utterly sucked, so I went back to dselect. GH Hmmm. I've been using it for 2 years and haven't found that to be the case at all. -- Raquel We are so accustomed to disguise ourselves to others that in the end we become disguised to ourselves. --Francois de la Rochefoucauld -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
On Wed, May 17, 2006 at 02:59:26PM +0200, H. Wilmer wrote: Florian Kulzer wrote: You cannot break anything by using aptitude and apt-get together, but you will (partially) neutralize many of the advantages of aptitude. Just think of aptitude as a tool which integrates the functionality of apt-get, apt-cache, etc. into one utility with an optional ncurses-GUI and a broader repertoire for the resolution of dependency problems. Hm, I tried aptitude and found that you won't know what's going on anymore and that it tries to do things to packages you won't want it to do and that it's impossible to prevent that and very difficult, if not impossible, to make it install the packages you want. When using it after a fresh install, it appears to leave you with a totally broken system. In other words: Aptitude just utterly sucked, so I went back to dselect. With all the talk about aptitude and synaptic being the Ultimate way to go, I'm glad to see other people using apt-get from the command line and dselect for a front-end. I learned dselect and couldn't get myself to learn aptitude, so I guess I would say dselect's easier to use ;) -- Christopher Nelson -- [EMAIL PROTECTED] --- Anybody want a binary telemetry frame editor written in Perl? -- Larry Wall in [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
Christopher Nelson wrote: On Wed, May 17, 2006 at 02:59:26PM +0200, H. Wilmer wrote: Florian Kulzer wrote: You cannot break anything by using aptitude and apt-get together, but you will (partially) neutralize many of the advantages of aptitude. Just think of aptitude as a tool which integrates the functionality of apt-get, apt-cache, etc. into one utility with an optional ncurses-GUI and a broader repertoire for the resolution of dependency problems. Hm, I tried aptitude and found that you won't know what's going on anymore and that it tries to do things to packages you won't want it to do and that it's impossible to prevent that and very difficult, if not impossible, to make it install the packages you want. When using it after a fresh install, it appears to leave you with a totally broken system. In other words: Aptitude just utterly sucked, so I went back to dselect. With all the talk about aptitude and synaptic being the Ultimate way to go, I'm glad to see other people using apt-get from the command line and dselect for a front-end. I learned dselect and couldn't get myself to learn aptitude, so I guess I would say dselect's easier to use ;) One thing thats always confused me with aptitude is how to 'unmark' packages that I have accidently marked when uses the ncurses interface. I have no trouble marking things and installing them, although, I generally use the command line for this. It usually when I have a lot of upgrades and I'd like to mark them all, and then unmark the few that I wannt to skip in upgrading, that I strike this problem of not knowing how to umark marked packages. Chris L. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
switching from apt-get to aptitude
I've googled this quite a bit and found various web pages praising aptitude as a better apt-get. But I've also seen cautions about mixing the two. I'm running a testing installation that has been in place for nearly two years -- all the while maintained via apt-get. I've even written a shell wrapper around apt-get to log what gets installed. But the above mentioned sites make switching over to aptitude sound good. I can't seem to find a definitive answer on whether or not this is a good idea. And I haven't found any kind of howto for doing the switch well. I have seen some sites that indicate aptitude may attempt to remove lots of packages on the first run after such a switch-over. If it's just a start-up kind of problem, can this be worked around? (i.e. marking packages in some way that means no, really! I've installed that and want to keep it!) Any advice, or perhaps pointers to better articles than what I've found? Thanks, Rick Reynolds -- If you don't know the truth, you will believe anything. -- Eric Simmons -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
On (16/05/06 11:53), Rick Reynolds wrote: I've googled this quite a bit and found various web pages praising aptitude as a better apt-get. But I've also seen cautions about mixing the two. I'm running a testing installation that has been in place for nearly two years -- all the while maintained via apt-get. I've even written a shell wrapper around apt-get to log what gets installed. But the above mentioned sites make switching over to aptitude sound good. I can't seem to find a definitive answer on whether or not this is a good idea. And I haven't found any kind of howto for doing the switch well. I have seen some sites that indicate aptitude may attempt to remove lots of packages on the first run after such a switch-over. If it's just a start-up kind of problem, can this be worked around? (i.e. marking packages in some way that means no, really! I've installed that and want to keep it!) Any advice, or perhaps pointers to better articles than what I've found? Aptitude is a front end to apt and offers suggestions to stop you installing broken packages and other useful functions. I use aptitude and apt-listbugs to maintain my two sid systems and have kept out of serious trouble as a result. The problem with mixing aptitude with apt is that aptitude will sometimes threaten to remove packages it thinks are dependencies becuase it wasn't used to install them. However, you can override its suggestions. If you use it exclusively, it won't threaten to do so, unless you use Shift-M Once you've switched, you won't regret it :) I see apt-get as the macho way to update your system . ducks quickly Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
Rick Reynolds: I've googled this quite a bit and found various web pages praising aptitude as a better apt-get. But I've also seen cautions about mixing the two. Mixing the two is generally a bad idea since aptitude tracks which packages you really wanted to install and which ones just have been pulled in as dependencies. For example, a few days ago I decided to take a look at KDE (I am a long time IceWM user). I just did 'aptitude install kde' and had almost several hundred MB worth of k* applications. Exactly what I wanted and, so far, exactly what apt-get would have done. But it was just an experiment and I wanted to get rid of KDE again. Aptitude allowed me to just 'aptitude purge kde' again and it removed *every* package kde depended on. If I had used apt-get to install and remove kde, apt-get would just have removed the package kde (size: 7kB) and not its numerous dependencies. I can't seem to find a definitive answer on whether or not this is a good idea. And I haven't found any kind of howto for doing the switch well. I have seen some sites that indicate aptitude may attempt to remove lots of packages on the first run after such a switch-over. If it's just a start-up kind of problem, can this be worked around? (i.e. marking packages in some way that means no, really! I've installed that and want to keep it!) Yes, that is possible, but it takes some time to do that. I usually use aptitude's command line interface (which is almost exactly like apt-get's interface, only better), but initially it is probably best to run aptitude interactively (ie. without any arguments). You have to press 'u' (equialent to 'apt-get update') and then 'g'. This tells aptitude to propose actions. Then you will probably be presented with a lot of packages that aptitude wants to remove. Now just select every package you want to keep and press 'm'. This marks this package as manually installed (as opposed to automatically installed via a dependency). Pressing g again will make aptitude recalculate its actions again or process them immediately (I cannot tell exactly when it does what). J. -- I eat meat and am concerned about bugs which are resistant to antibiotics. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: switching from apt-get to aptitude
On Tue, 2006-05-16 at 20:02 +0200, Jochen Schulz wrote: Rick Reynolds: [snip] For example, a few days ago I decided to take a look at KDE (I am a long time IceWM user). I just did 'aptitude install kde' and had almost several hundred MB worth of k* applications. Exactly what I wanted and, so far, exactly what apt-get would have done. But it was just an experiment and I wanted to get rid of KDE again. Aptitude allowed me to just 'aptitude purge kde' again and it removed *every* package kde depended on. If I had used apt-get to install and remove kde, apt-get Even X? -- - Ron Johnson, Jr. Jefferson, LA USA Anyone who says he won't resign four times, will. John Kenneth Galbraith -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
Ron Johnson: On Tue, 2006-05-16 at 20:02 +0200, Jochen Schulz wrote: For example, a few days ago I decided to take a look at KDE (I am a long time IceWM user). I just did 'aptitude install kde' and had almost several hundred MB worth of k* applications. Exactly what I wanted and, so far, exactly what apt-get would have done. But it was just an experiment and I wanted to get rid of KDE again. Aptitude allowed me to just 'aptitude purge kde' again and it removed *every* package kde depended on. If I had used apt-get to install and remove kde, apt-get Even X? Of course not! But you are right, I should have made myself more clear: aptitude removed every package kde depended upon *that were not yet installed* when I requested installation of kde. J. -- I have been manipulated and permanently distorted. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: switching from apt-get to aptitude
On Tue, May 16, 2006 at 11:53:46AM -0400 or thereabouts, Rick Reynolds wrote: I've googled this quite a bit and found various web pages praising aptitude as a better apt-get. But I've also seen cautions about mixing the two. You might try searching the archives for articles confirming what I'm saying; You wouldn't necessarily mix the two, but the two can be installed on the same machine -- Mine are. I don't use apt-get, and simply run aptitude from the command line. It works much the same as the apt-get command. I've run command line aptitude for several years without any problem in doing so. In fact, it was on this list that I read an e-mail by a revered member of this list, (can't remember offhand whom it was) who indicated that aptitude handled dependencies and management better than apt-get can. -- Regards Stephen + You tread upon my patience. -- William Shakespeare, Henry IV + signature.asc Description: Digital signature
Re: switching from apt-get to aptitude
On Tue, May 16, 2006 at 15:45:05 -0400, Stephen wrote: On Tue, May 16, 2006 at 11:53:46AM -0400 or thereabouts, Rick Reynolds wrote: I've googled this quite a bit and found various web pages praising aptitude as a better apt-get. But I've also seen cautions about mixing the two. You might try searching the archives for articles confirming what I'm saying; You wouldn't necessarily mix the two, but the two can be installed on the same machine -- Mine are. I don't use apt-get, and simply run aptitude from the command line. It works much the same as the apt-get command. Aptitude depends on libapt-pkg-libc6, which is currently provided by the apt package, therefore you will always have apt(-get) installed along with aptitude. (Maybe that will change in the future, or the apt-get command will be dropped from the apt package?) You cannot break anything by using aptitude and apt-get together, but you will (partially) neutralize many of the advantages of aptitude. Just think of aptitude as a tool which integrates the functionality of apt-get, apt-cache, etc. into one utility with an optional ncurses-GUI and a broader repertoire for the resolution of dependency problems. An improved search interface, logging, and keeping track of automatically installed packages are additional goodies thrown in the mix. I've run command line aptitude for several years without any problem in doing so. In fact, it was on this list that I read an e-mail by a revered member of this list, (can't remember offhand whom it was) who indicated that aptitude handled dependencies and management better than apt-get can. Another thing to keep in mind is that apt-get has Super Cow Powers, while aptitude does not have them. (Try apt-get moo and compare this to aptitude moo. Also check the effect of increasing the verbosity with aptitude, i.e. add the options -v, -vv, etc.) -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
For example, a few days ago I decided to take a look at KDE (I am a long time IceWM user). I just did 'aptitude install kde' and had almost several hundred MB worth of k* applications. Exactly what I wanted and, so far, exactly what apt-get would have done. But it was just an experiment and I wanted to get rid of KDE again. Aptitude allowed me to just 'aptitude purge kde' again and it removed *every* package kde depended on. If I had used apt-get to install and remove kde, apt-get Even X? Of course not! But you are right, I should have made myself more clear: aptitude removed every package kde depended upon *that were not yet installed* when I requested installation of kde. Question for you (anyone) then: If you install kde through aptitude, an aptitude marks Xorg as a dependency, and then install gnome a couple of days later, would removing kde also remove Xorg, or would it see it as a current dependency for gnome and leave it?
Re: switching from apt-get to aptitude
On Tue, May 16, 2006 at 10:31:40PM +0200, Florian Kulzer wrote: On Tue, May 16, 2006 at 15:45:05 -0400, Stephen wrote: On Tue, May 16, 2006 at 11:53:46AM -0400 or thereabouts, Rick Reynolds wrote: I've googled this quite a bit and found various web pages praising aptitude as a better apt-get. But I've also seen cautions about mixing the two. You might try searching the archives for articles confirming what I'm saying; You wouldn't necessarily mix the two, but the two can be installed on the same machine -- Mine are. I don't use apt-get, and simply run aptitude from the command line. It works much the same as the apt-get command. Aptitude depends on libapt-pkg-libc6, which is currently provided by the apt package, therefore you will always have apt(-get) installed along with aptitude. (Maybe that will change in the future, or the apt-get command will be dropped from the apt package?) You cannot break anything by using aptitude and apt-get together, but you will (partially) neutralize many of the advantages of aptitude. Just think of aptitude as a tool which integrates the functionality of apt-get, apt-cache, etc. into one utility with an optional ncurses-GUI and a broader repertoire for the resolution of dependency problems. An improved search interface, logging, and keeping track of automatically installed packages are additional goodies thrown in the mix. I've run command line aptitude for several years without any problem in doing so. In fact, it was on this list that I read an e-mail by a revered member of this list, (can't remember offhand whom it was) who indicated that aptitude handled dependencies and management better than apt-get can. Another thing to keep in mind is that apt-get has Super Cow Powers, while aptitude does not have them. (Try apt-get moo and compare this to aptitude moo. Also check the effect of increasing the verbosity with aptitude, i.e. add the options -v, -vv, etc.) Florian, between muttrc bits, valiant attempts at starting a flame-war and now this, you sir on permanently on my Fan list. ROTFLMAO A signature.asc Description: Digital signature
Re: switching from apt-get to aptitude
Grant Thomas schreef: For example, a few days ago I decided to take a look at KDE (I am a long time IceWM user). I just did 'aptitude install kde' and had almost several hundred MB worth of k* applications. Exactly what I wanted and, so far, exactly what apt-get would have done. But it was just an experiment and I wanted to get rid of KDE again. Aptitude allowed me to just 'aptitude purge kde' again and it removed *every* package kde depended on. If I had used apt-get to install and remove kde, apt-get Even X? Of course not! But you are right, I should have made myself more clear: aptitude removed every package kde depended upon *that were not yet installed* when I requested installation of kde. Question for you (anyone) then: If you install kde through aptitude, an aptitude marks Xorg as a dependency, and then install gnome a couple of days later, would removing kde also remove Xorg, or would it see it as a current dependency for gnome and leave it? In that case it knows that gnome depends on it, so it doesn't remove it. -- If I have been able to see further, it was only because I stood on the shoulders of giants. -- Isaac Newton Roel Schroeven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: switching from apt-get to aptitude
Grant Thomas wrote: Question for you (anyone) then: If you install kde through aptitude, an aptitude marks Xorg as a dependency, and then install gnome a couple of days later, would removing kde also remove Xorg, or would it see it as a current dependency for gnome and leave it? Aptitude does not mark Xorg as a dependency - it already knows the dependencies from the package information. What aptitude records is whether a package was automatically installed as a dependency of a package that it was asked to install. When aptitude removes a package, it looks if there are any packages marked as automatically installed that no other package depends on, and if so it will remove them. Aptitude will never remove a dependency if it is still needed by another package (unless you force it), as that would leave your system in a broken state. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
