On Sun, Aug 03, 2025 at 12:53:45PM +0200, Da4ndo wrote: > The package’s defaults and configs are intentionally general and aimed at > common, widely used setups. Users who need something different can easily > adjust them. > As mentioned before, I plan to keep updating it with more features, but I > don’t live my life around this single package — still, both I and people I > know find Hyde-Ext useful.
OK, fair enough. > It is intentionally designed to install a prebuilt binary to speed up > installation. If someone prefers building from source, they can get the > source from GitHub and build it themselves. I also plan to publish a -git > AUR variant, similar to what’s done for hyprproxlock. The binary is built > using a GitHub Actions workflow. Binary packages are allowed, however my point was that according to the guidelines, these should have a `-bin` suffix, and if not, then should build from sources. This package (and the others I pointed out) lack this suffix, so it should build from sources. > The missing description was due to a prior workflow issue. In my opinion, > most users check the project’s GitHub or website before installing from > AUR, rather than relying solely on the PKGBUILD description. Everything is > still in line with AUR rules. It's still useful to read the description in the AUR page to have an idea of what the software does, and it's an easy fix though.
