Closed RubenKelevra closed 1 month ago
Maybe unrelated but
% aura -As firefox --reverse | tail -n 20
results are strange, considering search results are sorted by votes by default:
aur/firefox-esr-i18n-sr 128.0-1 (49 | 1.52)
Standalone web browser from mozilla.org, Extended Support Release
aur/firefox-esr-i18n-pl 128.0-1 (49 | 1.52)
Standalone web browser from mozilla.org, Extended Support Release
aur/firefox-esr-i18n-gd 128.0-1 (49 | 1.52)
Standalone web browser from mozilla.org, Extended Support Release
aur/firefox-esr-i18n-da 128.0-1 (49 | 1.52)
Standalone web browser from mozilla.org, Extended Support Release
aur/firefox-esr-i18n-zh-cn 128.0-1 (49 | 1.52)
Standalone web browser from mozilla.org, Extended Support Release
aur/firefox-esr-i18n-gn 128.0-1 (49 | 1.52)
Standalone web browser from mozilla.org, Extended Support Release
aur/firefox-esr-i18n-cs 128.0-1 (49 | 1.52)
Standalone web browser from mozilla.org, Extended Support Release
aur/firefox-esr-i18n-ff 128.0-1 (49 | 1.52)
Standalone web browser from mozilla.org, Extended Support Release
aur/firefox-esr-bin 128.0-1 (162 | 1.01)
Standalone web browser from mozilla.org - Extended Support Release
aur/firefox-kde-opensuse 127.0-1 (334 | 0.00)
Standalone web browser from mozilla.org with OpenSUSE patch, integrate better with KDE
comparison with
% paru -Ss firefox | tail -n 20
aur/lastpass 4.125.0.4-1 [+94 ~0.00]
The Universal LastPass installer for Firefox, Chrome, and Opera
aur/librewolf 128.0.3-1 [+131 ~8.65]
Community-maintained fork of Firefox, focused on privacy, security and freedom.
aur/palemoon 1:33.2.1-1 [+141 ~0.00]
Open source web browser based on Firefox focusing on efficiency.
aur/firefox-esr-bin 128.0-1 [+162 ~1.01]
Standalone web browser from mozilla.org - Extended Support Release
aur/palemoon-bin 1:33.2.0-1 [+196 ~0.50] [Out-of-date: 2024-07-16]
Open source web browser based on Firefox focusing on efficiency.
aur/icecat 115.12.0-1 [+250 ~0.17] [Out-of-date: 2024-07-09]
GNU version of the Firefox ESR browser
aur/firefox-kde-opensuse 127.0-1 [+334 ~0.00] [Out-of-date: 2024-07-27]
Standalone web browser from mozilla.org with OpenSUSE patch, integrate better with KDE
aur/librewolf-bin 128.0.3-1 [+372 ~16.54]
Community-maintained fork of Firefox, focused on privacy, security and freedom.
aur/firefox-beta-bin 129.0rc1-1 [+398 ~0.01]
Standalone web browser from mozilla.org - Beta
aur/firefox-nightly 130.0a1+20240723.1+h17630c12ac58-1 [+609 ~0.16]
Fast, Private & Safe Web Browser (Nightly version)
aur/tor-browser-bin 13.5.1-1 [+1281 ~2.07]
Tor Browser Bundle: anonymous browsing using Firefox and Tor
I'd expect to see firefox-nightly
, firefox-beta-bin
, librewolf-bin
before firefox-esr-bin
considering they have many more votes, but they're not even listed (even without | tail -n 20
).
Aura can't handle dashes in the search term
For that, search by each term individually.
> aura -As firefox extension --limit 5
aur/firefox-extension-arch-search 1.0.5-2 (18 | 0.02)
A set of Web Extensions that adds ArchLinux (bug tracker, forum, packages, wiki, AUR) as a search engine to the Firefox browser.
aur/firefox-extension-greasemonkey 4.11-1 (17 | 0.00)
Customize the way a web page displays or behaves, by using small bits of JavaScript.
aur/chrome-token-signing 1:1.1.5.547-1 (15 | 0.00)
Chrome and Firefox extension for signing with your eID on the web
aur/firefox-extension-keepassxc-browser 1.9.1.1-1 (12 | 0.00)
Official browser plugin for the KeePassXC password manager.
aur/firefox-extension-plasma-integration-bin 1.9.1-2 (7 | 0.12)
Multitask efficiently by controlling browser functions from the Plasma desktop.
aura -As firefox --reverse | tail -n 20
You can use --limit
instead of a manual tail
.
I'd expect to see firefox-nightly, firefox-beta-bin, librewolf-bin before firefox-esr-bin
Confirmed. This isn't Aura's fault per se but something in the Faur. I'll look into it.
For that, search by each term individually.
Errrr the issue here is not, that you can't do something different, the issue is, that it breaks the principle of the least astonishment. One should be able to search for a package name, without having to remove the dashes.
Apart from that, it's not the same thing, because the order of the search words is not preserved:
$ paru -Ss --aur extension-firefox
$ aura -As extension firefox --limit 5
aur/firefox-extension-arch-search 1.0.5-2 (18 | 0.02)
A set of Web Extensions that adds ArchLinux (bug tracker, forum, packages, wiki, AUR) as a search engine to the Firefox browser.
aur/firefox-extension-greasemonkey 4.11-1 (17 | 0.00)
Customize the way a web page displays or behaves, by using small bits of JavaScript.
aur/chrome-token-signing 1:1.1.5.547-1 (15 | 0.00)
Chrome and Firefox extension for signing with your eID on the web
aur/firefox-extension-keepassxc-browser 1.9.1.1-1 (12 | 0.00)
Official browser plugin for the KeePassXC password manager.
aur/firefox-extension-plasma-integration-bin 1.9.1-2 (7 | 0.12)
Multitask efficiently by controlling browser functions from the Plasma desktop.
This leads to wildly different search results, depending on the term:
As mentioned above, Aura 4 uses its own metadata server. From the faur
README:
Caveat:
by=desc
is term-based, not regex based. This is for performance reasons. So,packages?names=aura&by=desc
will match on aura-bin but not on auralcap.
To vastly improve performance in the term-based search case, regex/substring-based searching is not possible. I realise this may be surprising and I apologise for that. The difference is simply due to the other package managers calling the AUR API directly. The Faur does other things that the AUR API does not, but to enable those this sacrifice was made.
The issue of firefox-nightly
etc. not appearing in the search terms has been fixed on the Faur side. If you try the search again you should be able to see that in your current version of Aura.
As mentioned above, Aura 4 uses its own metadata server. From the
faur
README:Caveat:
by=desc
is term-based, not regex based. This is for performance reasons. So,packages?names=aura&by=desc
will match on aura-bin but not on auralcap.To vastly improve performance in the term-based search case, regex/substring-based searching is not possible. I realise this may be surprising and I apologise for that. The difference is simply due to the other package managers calling the AUR API directly. The Faur does other things that the AUR API does not, but to enable those this sacrifice was made.
Can we get a fallback option then? It's for all intents and purposes a regression to be incapable of searching for a direct package name at all. At least let a search reach out to the normal AUR api which seems to be stronger here if the user asks for it.
If you search for a direct package name, it will find it. More specifically, if you pass multiple terms, like:
aura -As nintendo switch
Then any package which contains both nintendo
and switch
anywhere in its name, description, or keywords will be returned. Package names are split on -
and _
for individual terms. There is then a cleaning process that strips off various symbols and filters out terms that are too short, etc. What remains form "indexes" by which future lookups are very fast, especially for compound searches as shown above. This is basically the main sell of the Faur, along with its ability to do "provides"-based lookups for dependency resolution.
The downside of this, as shown already, is that a search like aura -As nint
will not yield Nintendo-related packages.
To vastly improve performance in the term-based search case, regex/substring-based searching is not possible. I realise this may be surprising and I apologise for that. The difference is simply due to the other package managers calling the AUR API directly. The Faur does other things that the AUR API does not, but to enable those this sacrifice was made.
I read about this, and I can see the benefit of using a dedicated server for this. But I can't really follow your argument why it can't search for full package names or substrings of that, if they contain a minus.
I mean, just do it like grep: By default search for the string byte-wise or basic regex, and if the user wants to use Regex he/she can specify '-E':
Pattern Syntax
-E, --extended-regexp
Interpret PATTERNS as extended regular expressions (EREs, see below).
-F, --fixed-strings
Interpret PATTERNS as fixed strings, not regular expressions.
-G, --basic-regexp
Interpret PATTERNS as basic regular expressions (BREs, see below). This is the default.
Btw grep
has no issue with minus even if searching with extended regex:
$ paru -Ss firefox | /usr/bin/grep --basic-regexp "firefox-nightly" | head -n 10
aur/firefox-nightly-en-gb 115.0a1.20230517.153544-1 [+1 ~0.00] [Orphaned]
aur/firefox-nightly-i18n-zh-tw 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-zh-cn 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-xh 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-vi 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-uz 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-ur 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-uk 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-trs 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-tr 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
$ paru -Ss firefox | /usr/bin/grep --extended-regexp "firefox-nightly" | head -n 10
aur/firefox-nightly-en-gb 115.0a1.20230517.153544-1 [+1 ~0.00] [Orphaned]
aur/firefox-nightly-i18n-zh-tw 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-zh-cn 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-xh 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-vi 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-uz 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-ur 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-uk 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-trs 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
aur/firefox-nightly-i18n-tr 106.0a1.20220827.173411-1 [+10 ~0.09] [Out-of-date: 2023-04-11] [Orphaned]
Then any package which contains both
nintendo
andswitch
anywhere in its name, description, or keywords will be returned. Package names are split on-
and_
for individual terms.
Why not also add sections of multiple words to the index?
Like firefox-nightly-i18n-xh
is adding these instead of just the individual words:
firefox
nightly
i18n
xh
firefox-nightly
firefox-nightly-i18n
firefox-nightly-i18n-xh
i18n-xh
nightly-i18n-xh
nightly-i18n
One easy compromise is for Aura, on its end, to split the search input and send the split query to the Faur instead. So:
aura -As firefox-extension
would yield the same results as
aura -As firefox extension
As discussed, the above two searches now yield the same results.
I've released 4.0.1
, I'm going to close this. Thanks again for reporting the issue.
I'm currently using Aura 4.0.0, and I noticed that Aura can't handle dashes in the search term, if searching the AUR:
Despite there being search results: