docs: add aurscan-manticore-bin-release-git AUR package and help wanted - #32
Conversation
Add the binary release package as an install option alongside the existing source-built package. No build dependencies needed — installs pre-built release binaries with GPG tag verification.
HaleTom
changed the title
|
General packaging guidelines for the aur would be that you have
This naming consistency helps users of the AUR know what to expect when using a particular PKGBUILD. It's generally accepted that |
|
I will just reach out to the |
|
Thank you much @HaleTom for work, time and interest! I appreciate you. |
|
@manticore-projects thanks! You're most welcome. I'm finding that sometimes the desire to help turns into much more than expected to do it best-practice-wise. But this is definitely worth doing. Arch users don't give away GitHub stars as quickly as others. And 100 already means that we're doing the Lord's Work :-P |
3 participants
Summary
Add the
aurscan-manticore-bin-release-gitAUR package to the README install and acknowledgements sections.Changes
Install section — restructured from a single package to a two-row table listing both AUR variants:
aurscan-manticore-bin-release-gitaurscan-manticore-release-gitThe install command example now shows the
-bin-releasepackage first (lower barrier to entry — no toolchain), with the source-build package as the alternative.Acknowledgements — updated the AUR package mention from a single package to both:
Rationale
The
-bin-releasepackage exists on the AUR and offers the same functionality without requiring Go as a build dependency. It fetches pre-built release binaries and verifies the upstream release tag's GPG signature using the same bundled-key +gpgvapproach. Listing it gives users a no-toolchain install path.Both packages track the latest release tag, not bleeding-edge
main— this is already stated and applies to both.Verification
aur.archlinux.org/packages/aurscan-manticore-bin-release-git)