| Summary: | emerge -s should not require @ when category is specified | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Martin Mokrejš <mmokrejs> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | bugzilla |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Martin Mokrejš
2009-06-05 14:18:19 UTC
You should use eix for searching anyway. really? what's emerge -s for then? i've never used eix in 3.5 years and really curious about the reason for eix being the portage search tool now On the other hand: Why not use eix? I was sceptical too before I tried it, nowadays it's simply the only thing I can think of when wanting to search for a package. emerge -s is like grep, eix is like ack - simply better in all ways. Once you've tried it you wonder why you'd ever want to use the alternative.
Besides, from the emerge man page:
"--search (-s)
Searches for matches of the supplied string in the portage tree."
So I'd guess that it only searches the tree by design. Overlays are not always officially supported by gentoo, so why would their tool for packages list unknown and potentially dangerous atoms? The current behaviour seems reasonable to me.
(In reply to comment #0) > nfssrv ~ # emerge -s sys-cluster/empi You have to prepend @ if you are going to include the category in the search. This is documented in `man emerge`. (In reply to comment #4) > (In reply to comment #0) > > nfssrv ~ # emerge -s sys-cluster/empi > > You have to prepend @ if you are going to include the category in the search. > This is documented in `man emerge`. Hmm, but the '/' won't ever be in the package name, so emerge can safely fix that on my behalf and treat the substring in front of the slash as category, right? ;) (In reply to comment #3) > Besides, from the emerge man page: > "--search (-s) > Searches for matches of the supplied string in the portage tree." > > So I'd guess that it only searches the tree by design. Overlays are not always > officially supported by gentoo, so why would their tool for packages list > unknown and potentially dangerous atoms? The current behaviour seems > reasonable to me. It should be simple to print a warning if emerge is not going to search through overlays, it knows from make.conf I use them ... if this was really the intent. (In reply to comment #5) > Hmm, but the '/' won't ever be in the package name, so emerge can safely fix > that on my behalf and treat the substring in front of the slash as category, > right? ;) That seems reasonable. |
