| 1 |
Hi Grant, |
| 2 |
|
| 3 |
On 2018-09-17 20:10, Grant Edwards wrote: |
| 4 |
> I recently noticed that "emerge --search" stopped working correctly. |
| 5 |
> It now returns all sorts of packages that don't match the search |
| 6 |
> sting: |
| 7 |
> |
| 8 |
> $ emerge --search wxpython | grep '^[^\t ]' |
| 9 |
> |
| 10 |
> [ Results for search key : wxpython ] |
| 11 |
> Searching... |
| 12 |
> * dev-lang/python |
| 13 |
> * dev-python/bpython |
| 14 |
> * dev-python/ipython |
| 15 |
> * dev-python/pythong [ Masked ] |
| 16 |
> * dev-python/twython |
| 17 |
> * dev-python/vpython [ Masked ] |
| 18 |
> * dev-python/wxpython |
| 19 |
> [ Applications found : 7 ] |
| 20 |
> |
| 21 |
> Why is it returning packges that don't match what I'm searching for? |
| 22 |
> |
| 23 |
> Shouldn't only the last of the ones shown above be returned? |
| 24 |
|
| 25 |
the culprit is --fuzzy-search. The manual states: "This option is |
| 26 |
enabled by default". |
| 27 |
|
| 28 |
Try the following: |
| 29 |
|
| 30 |
$ emerge --fuzzy-search=n --search wxpython | grep '^[^\t ]' |
| 31 |
[ Results for search key : wxpython ] |
| 32 |
Searching... |
| 33 |
* dev-python/wxpython |
| 34 |
[ Applications found : 1 ] |
| 35 |
|
| 36 |
I don't use --search (eix is my friend), but if you are certain that |
| 37 |
this behavior is new to you, then this new default must be introduced |
| 38 |
only recently. |
| 39 |
|
| 40 |
-- |
| 41 |
Kind regards |
| 42 |
|
| 43 |
Flo |
Archives