Seth Vidal wrote:
On Wed, 6 May 2009, Gerry Reno wrote:
Seth Vidal wrote:
On Wed, 6 May 2009, Gerry Reno wrote:
The man page says that 'installed' is a valid context and that's
been in there for quite a long while from what I can see. Why do
you want to put more restriction into this tool? Yum can list
installed as well as available packages. Repoquery has been able
and should continue to be able to do the same thing.
B/c it is not called 'rpmdb query' and it confuses results when you
look up a package and it spits back out something from your local
rpmdb.
So restricting it to only doing what it is named for makes the most
sense to me.
Who cares what the tool name is? The tool has a good set of
functionality and to now start restricting that functionality b/c it
doesn't exactly match the name of the tool is crazy. Maybe the tool
should have been named 'pkgquery' or something like that but really
who cares. I don't want to see a good tool neutered because of a
naming issue. Please don't do this. It's clear that the author
intended this tool to have the scope outlined in the man page and
that includes working against the installed package set as well as
the repos.
The author can change things if he sees fit, he has check in access
for a reason but it doesn't match to my mind which is why I changed it.
-sv
Just change the NAME of the tool if this bothers you. Don't neuter the
tool for crying out loud. That's ridiculous.
Regards,
Gerry
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum
