Summary: | integrate qpkg functionality into emerge | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Mike Roest <gentoo> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | CC: | bugs-janitor, karltk, mholzer, mr_bones_, vapier |
Priority: | Lowest | ||
Version: | 2.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Mike Roest
2002-07-14 16:58:43 UTC
these features already exist `emerge gentoolkit` and then type `qpkg -h` Best to integrate this functionality into emerge at some point. If possible make the "-f" use regexps.. I more often get the question "what package provides foo" then "what packages provides /path/to/foo". So "What package provides "libhistory.so" ?" could be checked with ~$ emerge -f "*libhistory.so*" by ppl that think have this file on their system. -f is already taken by fetch ;) the prob with integrating qpkg with emerge is we start to run out of cmdline opts ... then they get more obscure and it kinda becomes a pain ... oh and you can do `qpkg -fp '*libhist*'` Something for portage-ng methinks. |