El Jueves, 7 de Julio de 2005 17:37, Bob Proulx escribió: > Alejandro Exojo wrote: > > 1. aptitude > > Unfortunately that brings up an interactive GUI. I have far too many > machines to interactively babysit each and every one of them > uniquely. It is just not practical.
Yes, I understand that using the GUI requires interaction, and this is against automation, but I still think that the GUI is only required in complicated upgrades, because it has the benefit of working in two steps: 1) marking actions and 2) seeing the effect of those individually, and correcting them if needed before following. > What are different ways to use aptitude which would be bad? What is > an incorrect way to use aptitude? I can't really think of any. So > this statement leaves me not knowing what is being discussed. To be > clear I am talking about these commands. Are any of these incorrect > use of aptitude? If so why? I was thinking more in mixing the use of aptitude, and apt-get. I mean, aptitude stores some extra information in /var/lib/aptitude/pkgstates, that AFAIK is ignored by apt-get. -- Alex (a.k.a. suy) - GPG ID 0x0B8B0BC2 http://darkshines.net/ - Jabber ID: [EMAIL PROTECTED]
