Re: [gentoo-user] Re: How to disable fuzzy-search in emerge?
On Fri, 10 Apr 2020 17:00:08 - (UTC), Grant Edwards wrote: > I don't know why it didn't occur to me to check for a make.conf > variable instead of an environment variable or USE flag. Of course > now that I know that make.conf variable's name, I have found it in few > other places in the emerge man page, and there's a clear description > of it in make.conf(5). > > Unfortunately, the emerge man page doesn't really discuss make.conf > except for a few places where it's mentioned that some specific option > can be controlled via make.conf. Try the make.conf man page :) -- Neil Bothwick I spilled Spot remover on my dog. Now he's gone. pgpEaw3V_i1AB.pgp Description: OpenPGP digital signature
[gentoo-user] Re: How to disable fuzzy-search in emerge?
On 2020-04-10, Grant Taylor wrote: > I took pause for a moment wondering if this was something I typed or > not. ;-) I know what you mean. :) -- Grant (the other one)
Re: [gentoo-user] Re: How to disable fuzzy-search in emerge?
On 4/10/20 11:00 AM, Grant Edwards wrote: Yes, that works! Good. Thanks!! You're welcome. I don't know why it didn't occur to me to check for a make.conf variable instead of an environment variable or USE flag. Of course now that I know that make.conf variable's name, I have found it in few other places in the emerge man page, and there's a clear description of it in make.conf(5). Unfortunately, the emerge man page doesn't really discuss make.conf except for a few places where it's mentioned that some specific option can be controlled via make.conf. I often feel like the make.conf file is a collection of environment variables, almost as if the file was sourced prior to running emerge. As such, I have to realize that if something looks like an environment variable, it can probably go into the make.conf as such. -- Grant I took pause for a moment wondering if this was something I typed or not. ;-) -- Grant. . . . unix || die
Re: [gentoo-user] Re: How to disable fuzzy-search in emerge?
Grant Edwards wrote: > On 2020-04-10, Dale wrote: > >> Equery used to behave like emerge does now, and maybe always has. > Really? Equery used to do fuzzy search by default, where it returns > package that don't actually contain the search string? > > What I liked about emerge --search, is that it would show you both the > installed version and the available version. I never figured out how > to get equery to do that. > > -- > Grant > Equery used to do that but it was changed a few years or so ago. It requires a more precise search now or the use of wildcards. Look at the output of mine in previous reply and you can also see what is installed, what is available and it even shows if a package is masked or keyworded. The command and options are equery list -p to get that. If you use overlays a lot, add -o to that or -po will work. Equery is my go to tool since I run some things stable and some things unstable. Dale :-) :-)
[gentoo-user] Re: How to disable fuzzy-search in emerge?
On 2020-04-10, Grant Taylor wrote: > > On 4/10/20 10:08 AM, Grant Edwards wrote: >> Yes, I'm aware I can add "--fuzzy-search n" to make it act sane, but >> is there an environment variable or USE flag or _something_ to make >> emerge --search do the right thing by default? > Does adding it to EMERGE_DEFAULT_OPTS in /etc/portage/make.conf help? Yes, that works! Thanks!! I don't know why it didn't occur to me to check for a make.conf variable instead of an environment variable or USE flag. Of course now that I know that make.conf variable's name, I have found it in few other places in the emerge man page, and there's a clear description of it in make.conf(5). Unfortunately, the emerge man page doesn't really discuss make.conf except for a few places where it's mentioned that some specific option can be controlled via make.conf. -- Grant
[gentoo-user] Re: How to disable fuzzy-search in emerge?
On 2020-04-10, Dale wrote: > Equery used to behave like emerge does now, and maybe always has. Really? Equery used to do fuzzy search by default, where it returns package that don't actually contain the search string? What I liked about emerge --search, is that it would show you both the installed version and the available version. I never figured out how to get equery to do that. -- Grant
Re: [gentoo-user] Re: How to disable fuzzy-search in emerge?
Grant Edwards wrote: > On 2020-04-10, Alec Ten Harmsel wrote: >> On Fri, Apr 10, 2020, at 12:08, Grant Edwards wrote: >>> I really, really hate how emerge now returns bucketfulls of useless, >>> unrelated results when you do a search. WTF is the point of returning >>> a bunch of packages that don't contain the search string when there is >>> is a package name that match the search string exactly? >> This doesn't answer your question, but `eix' is way faster and I've been >> using it since I've started using Gentoo. > Yes, I should just use eix or equery instead, now that emerge --search > is broken by default. > > -- > Grant > Equery used to behave like emerge does now, and maybe always has. A few years ago equery changed tho. Example. You type in equery list -p firefox and it will only return exact matches to firefox. It doesn't even return firefox-bin unless you put a wildcard on the end. Like this: root@fireball / # equery list -p firefox * Searching for firefox ... [-P-] [M ] www-client/firefox-52.9.0:0 [-P-] [ ] www-client/firefox-68.6.1:0 [IP-] [ ] www-client/firefox-74.0.1:0 root@fireball / # equery list -p firefox* * Searching for firefox* ... [-P-] [M ] www-client/firefox-52.9.0:0 [-P-] [ ] www-client/firefox-68.6.1:0 [IP-] [ ] www-client/firefox-74.0.1:0 [-P-] [M ] www-client/firefox-bin-52.9.0:0 [-P-] [ ] www-client/firefox-bin-68.6.1:0 [-P-] [ ] www-client/firefox-bin-74.0.1:0 root@fireball / # I have found that each tool has its strengths. Equery is just better at some things. Since I tend to copy and paste from the output of emerge, I'm able to get the exact name of the package I want info on. I rarely use the wildcards but sometimes they help. Also, you can put wildcards on the front or in the middle too. I think there is a way to get it to list the description to but can't recall the option. There is also those q tools. I rarely use them but I've seen others post output from commands they ran and it is interesting. Sometimes they give info that is much better. Thing is, it's hard for this old dog to learn new tricks when I don't use them often. Maybe one of those will help, or point you in a better direction. Dale :-) :-)
[gentoo-user] Re: How to disable fuzzy-search in emerge?
On 2020-04-10, Alec Ten Harmsel wrote: > On Fri, Apr 10, 2020, at 12:08, Grant Edwards wrote: >> I really, really hate how emerge now returns bucketfulls of useless, >> unrelated results when you do a search. WTF is the point of returning >> a bunch of packages that don't contain the search string when there is >> is a package name that match the search string exactly? > > This doesn't answer your question, but `eix' is way faster and I've been > using it since I've started using Gentoo. Yes, I should just use eix or equery instead, now that emerge --search is broken by default. -- Grant
