[PRQ#75049] Deletion Request for hyde-ext
matthewq337 [1] filed a deletion request for hyde-ext [2]: a PKGBUILD for someone's personal dotfiles does not really meet the usefulness criteria of the AUR [1] https://aur.archlinux.org/account/matthewq337/ [2] https://aur.archlinux.org/pkgbase/hyde-ext/
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”* You apparently filed that request as if the package were just someone’s private configs—but *hyde‑ext* isn’t. It's a *component of the HyDE framework*, a well‑established *Arch Linux environment* used by hundreds (if not thousands) of people. You can use Hyde-Ext to quickly install, configure, and restore system presets, dev tools, wallpapers, firewall rules, and more GitHub <https://github.com/HyDE-Project/HyDE>. Your request completely ignores the fact that: - *hyde‑ext* is a standalone AUR package with its own PKGBUILD, releases, votes, and metadata; it’s clearly listed in the AUR and meets all submission requirements aur.archlinux.org <https://aur.archlinux.org/packages/hyde-ext?utm_source=chatgpt.com>. - The *AUR guidelines explicitly state* that deletion requests must provide *solid justification*, not just vague assumptions—especially since the package maintainer may rely only on the aur‑requests thread for context wiki.archlinux.org <https://wiki.archlinux.org/title/AUR_submission_guidelines?utm_source=chatgpt.com> . Here’s what *hyde-ext* actually *does*: - Provides *modular dotfiles and system configurations* for the HyDE environment—in essence, a centralized installer and *restoration utility* for user-selectable tools and settings. - Allows users to define *custom sets* of tools: editors, fonts, sys-configs, dev toolchains, wallpapers, firewall profiles—you name it—and install them with one command. - Includes *restore functionality*: lost configurations due to config wipes or system reinstall? Just rerun hyde-ext to pull everything back. - It’s *not “someone’s personal PKGBUILD”;* it’s fully configurable, transparent, and documented. Moreover, a major update is imminent that will greatly expand what users can do—adding *comprehensive documentation*, enhanced modularity, and functionality newly requested by community contributors. Your deletion request not only misrepresents the tool’s purpose, but *undermines the input of an entire user community* that relies on *hyde-ext* to bootstrap and maintain their HyDE environments. If you stand by your request after that process, fine. But filing a deletion request comes with *responsibility*, and right now, you're neglecting yours. HyDE is a mature, arch-native environment. *hyde-ext* is part of the HyDe experience and *serves a clear purpose*—removing it without due diligence is not only unfair, it’s *damaging the community infrastructure*. So please: *rescind your deletion request* immediately. *_________________________________________________________* *Da4ndo* Software Engineer — Backend & Full‑Stack Developer *Experienced in Rust, TypeScript, **Python, **C #, **C ++ ,**Go, Java* 📄 Portfolio & Blog: https://da4ndo.com 📧 contact@da4ndo.com <contact@da4ndo.com> <notify@aur.archlinux.org> ezt írta (időpont: 2025. aug. 2., Szo, 21:43):
matthewq337 [1] filed a deletion request for hyde-ext [2]:
a PKGBUILD for someone's personal dotfiles does not really meet the usefulness criteria of the AUR
[1] https://aur.archlinux.org/account/matthewq337/ [2] https://aur.archlinux.org/pkgbase/hyde-ext/
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
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 📧 contact@da4ndo.com <contact@da4ndo.com> a821 <a821@mail.de> 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
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.
Hi, I saw the normal and -git tag pattern in other packages and followed that approach, but thanks for clarifying about the -bin suffix. I’ll add a proper description with the next update. I’m just frustrated because it feels like matthewq337 spammed several packages with short, generic deletion requests and then never followed up on them. *_________________________________________________________* *Da4ndo* Software Engineer — Backend & Full‑Stack Developer *Experienced in Rust, TypeScript, **Python, **C #, **C ++ ,**Go, Java* 📄 Portfolio & Blog: https://da4ndo.com 📧 contact@da4ndo.com a821 <a821@mail.de> 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
Request #75049 has been Rejected by Muflone [1]: the maintainer expressed his reasons on the mailing list [1] https://aur.archlinux.org/account/Muflone/
participants (3)
-
a821
-
Da4ndo
-
notify＠aur.archlinux.org