Very Computer

But, glint was really good for when you didn't know exactly what you
wanted, you just looked at a categorized tree of what was not already
installed, saw what you wanted and installed it.

This new Gnome RPM program, IMHO is not good at all. First, it doesn't
filter out RPMs that are already installed. Second, it just shows their
name, you have to add it to a list and the query it individually just to
see which group it is in. Not good if you're just browsing through the
available packages, not knowing exactly what you want. But, if I knew
exactly what I wanted, rpm from the command line is a lot easier. Plus,
glint is no longer included in 6.0.

Did no one at RedHat think that people installed packages in this
"browsing" manner? Is there some feature of Gnome RPM that I am missing?
Is the Gnome project planning on adding filtering and categorization to
the list of RPMs to install?

-John

: Did no one at RedHat think that people installed packages in this
: "browsing" manner? Is there some feature of Gnome RPM that I am missing?
: Is the Gnome project planning on adding filtering and categorization to
: the list of RPMs to install?

Also, I don't want to install GNOME yet, but gnorpm requires gnome
libraries. I don't like this.

--


|AMDK6-2/300/Linux2.2.10 | http://www.geocities.com/SiliconValley/3319/   |
-Interstellar matter is a gas.

: If you don't like GNOME & gnorpm, you can try the kpackage which is the KDE
: counterpart of RPM GUI manager, otherwise just use the 'rpm' command line.

Wouldn't this be the same problem? What if I don't want to install KDE
either? A lot of people do want to have lightweight wms? so having
to install some big libraries for a "small" thing like rpm sounds like
quite an overkill. Glint, although rather coarse, at least used to work
without either.