From: Douglas Anderson <dja@gendja.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] equery: deprecate --category filtering in belongs
Date: Sun, 8 Feb 2009 14:07:08 +0900 [thread overview]
Message-ID: <efeb8d230902072107x4d88c029y64c1573219bd59c6@mail.gmail.com> (raw)
Hi, does anyone use --category filtering in equery belongs? I want to
get rid of it, or at least deprecate it. My reasoning:
* We use 'equery belongs' when don't know to what package a file
belongs. Even if we have a suspicion, most users would have to look up
the category of the package before typing it in.
* Even if you happen to know the exact category of the package that
installed the file (why are you using belongs?), typing
--category=app-portage takes more time than is saved by filtering by
category (about 5 seconds more by my unscientific test).
Even in a script setting, I see no use for this. The time saved is minuscule:
$ time equery belongs /usr/bin/equery --category app-portage
[ Searching for file(s) /usr/bin/equery in app-portage... ]
app-portage/gentoolkit-0.2.4.2-r1 (/usr/bin/equery)
real 0m4.002s
user 0m3.680s
sys 0m0.076s
$ time equery belongs /usr/bin/equery
[ Searching for file(s) /usr/bin/equery in *... ]
app-portage/gentoolkit-0.2.4.2-r1 (/usr/bin/equery)
real 0m4.205s
user 0m3.738s
sys 0m0.102s
* Lastly, it's confusing. belongs takes a filename as input, but you
can filter by category? All other modules that take can filter by
category take a pkgspec.
-Doug
next reply other threads:[~2009-02-08 5:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 5:07 Douglas Anderson [this message]
2009-02-08 5:21 ` [gentoo-portage-dev] equery: deprecate --category filtering in belongs Brian Harring
2009-02-08 6:30 ` Brian Harring
2009-02-08 7:05 ` Douglas Anderson
2009-02-08 16:11 ` Michael A. Smith
2009-02-09 2:26 ` Douglas Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=efeb8d230902072107x4d88c029y64c1573219bd59c6@mail.gmail.com \
--to=dja@gendja.com \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox