Hi, 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.
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. 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. Lastly, I could be mistaken, but it seems like *matthewq337* has been submitting nearly identical reasons for multiple packages, often with very brief and generic justifications. Regards, *_________________________________________________________* *Da4ndo* Software Engineer — Backend & Full‑Stack Developer *Experienced in Rust, TypeScript, **Python, **C #, **C ++ ,**Go, Java* 📄 Portfolio & Blog: https://da4ndo.com 📧 [email protected] <[email protected]> a821 <[email protected]> ezt írta (időpont: 2025. aug. 3., V, 11:17): > On Sat, Aug 02, 2025 at 11:37:47PM +0200, Da4ndo wrote: > > Hi matthewq337, > > > > I just read your deletion request for hyde‑ext—and I’m furious. Frankly, > > taking a shot at an AUR package without bothering to fully understand > what > > it is or how it works is irresponsible. > > > > You wrote: > > > > > “a PKGBUILD for someone’s personal dotfiles does not really meet the > > > usefulness criteria of the AUR” > > [...] > > It looks to me, by reading the description, that this installs a list of > "curated" (by whom?) packages and configurations, which for me it's very > personal, by definition. But maybe this is useful for others, I'm not > sure... > > However, the PKGBUILD should build from source and not install a binary > from your repo. The description is missing, and it should declare > depends (I see that it requires an AUR helper [1] at least). > > Some of your other packages have the same problem: they should build > from sources: project-cleaner, hyprproxlock, cengine. > > [1] > https://github.com/Da4ndo/Hyde-Ext/blob/main/src/install/packages.rs#L47 >
