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.
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.
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.
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.
