On 07/05/2007 10:36:33 AM, Osamu Aoki wrote:

All you have to do is bind some key and menu to run "dpkg -L %s" with
the currently highlighted installed package name with system command
so and pipe its output to the scrolling internal viewer(PAGER).

That would be fine for interactive use, but I'm never interested
in using aptitude interactively.  I always use it from the command line.

I use aptitude instead of the other command line tools because:
a) it seems more comprehensive -- I need learn only one tool, and
b) because it keeps track of automatically installed stuff
and so helps keep my system clean and tidy.  (OT: IMO most folks
who want to do package management interactively would be
better off using synaptic.)

Slightly OT:

As I've become more familiar with apt I notice that aptitude is
missing two other bits of functionality that keep it from being
the one-size-fits-all apt tool:

Virtual Packages:
Aptitude won't tell you much of anything at all about virtual
packages.  To find out what real package goes with a virtual
package, and consequently get a description (aptitude show)
of the package you need to use "apt-cache show".  (IIRC
somehow this leads me to the real package.)
In other words, you can't tell if you want to install
a virtual package because you can't get a description
of the package from aptitude.  (Again, this is from the
command line.)

I believe I have to use "apt-cache policy" to tell which
repository a package will come from.  So I can't use
aptitude to tell if some thing to be upgraded or held
back is from the security repository, or if something
new I might want to install is from non-free, etc.

Should I open a separate bug report for these or is
this bug report the "make aptitude the only tool you
need" bug report?

Sorry for the long email messages. I don't mean to complain.
I want to explain why I think these things would make
aptitude better.

Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein

Reply via email to