Yay brings interesting results, but Paru finds more results from the description than it does from the name - does anyone else have this issue?
Specifically, YAY brought me the server (3rd item) and the player (5th item) as well as pulling in the âplexampâ package and âplex-desktopâ at number 22.
Paru pulled in libmpc relevant because of âcomPLEX numbersâ⌠and a bunch of other spam without actually getting any application with PLEX in itâs name!!!
I tested with the default config - with âbottomupâ added, because it strangely isnât the default.
I often run into the question/âbug reportâ/support thing about spelling and words.
Perhaps the search phrase provided is too broad - which such fuzzy searches - searching in multiple coloumns - returns to broad an answer.
e.g. searching for plex - returns text containing both simplex and plex.
Not that it is an issue in this context - the same is used by those trying to inject malware into public repositories like npm and pypi as prominent examples.
I think itâs time to dig into the config - as yay isnât too great with the default either (the player and server were around result 40 to 50, as with paru).
Maybe thereâs an issue with the paru config syntaxâŚ
yay:
"sortby": "popularity",
"searchby": "name-desc",
paru
SortBy = votes
SearchBy = name
Paru ignores it all, mpc still comes first on âcomplexâ in the description.
One thing to notice is that paru sorts the repos - you get core first, aur last.
While yay seems to try to sort the output based upon ârelevanceâ.
Its probably up to taste ⌠but I prefer a âdumbâ search that does what its told.
Yes that means returning a positive on âcomplexâ when searching âplexâ.
In my parttime job - I am trying to educate my users to do exactly that.
It is not the softwareâs responsibility to figure out what the user meant - just present the result - if the result is not the expected - refine the search.
As for the plex example, the search seems to be a âcontainsâ phrase - which of course will return numerous false positives for words having the letters âplexâ in exactly that order in either description or name.
It would be okay if it would return results from ânameâ before returning other results from âdescriptionâ.
The annying part is that I donât seem to be able to pass a flag to search ONLY in the name. @Zesko so you found plex media server and players with that?
Summary
extra/ttf-ibmplex-mono-nerd 3.0.2-1 [3.47 MiB 87.66 MiB] (nerd-fonts)
Patched font IBM Plex Mono (Blex) from nerd fonts library
URL : https://github.com/ryanoasis/nerd-fonts
extra/ttf-ibm-plex 6.3.0-1 [0 B 57.20 MiB] [Installed]
IBM Plex Mono, Sans, and Serif
URL : https://github.com/IBM/plex
â
paru -x '^plex' is closer - but excludes repos.
Itâs a bit sad that pamac is the only tool to search them all (including flatpaks).
This is quite right - but also slightly annoying - but yes, as with âyayâ before I edited the config, the result would be around 46-48 in the running (with plex in the name).
PamacGUI gets Plex (flathub) first, then Plex-HTPC (Flathub) followed by AUR âplex-media-serverâ.
I canât figure out why I canât do: paru --searchby name "plex"
Yes, basically the developer wants Paru (unlike Yay) to be more akin to using pacmanâŚ
Pikaur is interesting, but again - yay just seems more convenient to enter a fuzzy search and see results.
Hmmm so overall, I wonât bother going back with Paru - Iâm really quite happy using yay, and sometimes adding a GUI Pamac search if I want to include flatpak alternatives.
