You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When regex mode was implemented, it was made with the assumption that packages did not have these symbols (to be fair, it looks like there is only one package that uses '@', and it is in the official Arch repos). The suggested (accepted?) resolution in the original issue thread is to remove the regex mode entirely.
However, I believe the solution does not have to be that drastic. Instead of supporting Extended Regex, it can be simplified to Basic Regex (see differences here). This would resolve the issue of current unsupported characters, as well as retain the functionality from the original wildcard request.
This seems like another relatively simple change, especially if I introduce static variables to easily define the "valid" characters in the PKGBUILD variables throughout the script.
The text was updated successfully, but these errors were encountered:
Original issue reported here
Current supported package attributes/definitions:
https://wiki.archlinux.org/index.php/PKGBUILD#Package_name
When regex mode was implemented, it was made with the assumption that packages did not have these symbols (to be fair, it looks like there is only one package that uses '@', and it is in the official Arch repos). The suggested (accepted?) resolution in the original issue thread is to remove the regex mode entirely.
However, I believe the solution does not have to be that drastic. Instead of supporting Extended Regex, it can be simplified to Basic Regex (see differences here). This would resolve the issue of current unsupported characters, as well as retain the functionality from the original wildcard request.
This seems like another relatively simple change, especially if I introduce static variables to easily define the "valid" characters in the PKGBUILD variables throughout the script.
The text was updated successfully, but these errors were encountered: