FAQ
Frequently Asked Questions & Misc
Why not contribute Upstream?
Unfortunately, with the mass adoption of Flatpaks, most developers have no interest in AppImages or other formats
The few who do, either lack the interest, skill or time, or all of these to provide a properly made Portable Package. There are numerous examples, you simply need to see their issues tab & search our usernames.
So, creating PR that the upstream won't even accept is a huge waste of our time. However, we (mostly @Samueru-sama) still try our best to contribute upstream whenever possible.
Why not contribute & collaborate with AM?
We (@pkgforge) & AM's Author are friends.
AM has added partial support for some of PkgForge's Reposotories since
Nov 10, 2024
, thanks to this Issue: https://github.com/ivan-hc/AM/issues/1079So everything listed below is meant for a technical comparision & NOT to harass/insult either side. So please be decent & don't misquote us.
AM is a giant beast, & . This makes it very hard, if not impossible, to create CLI/GUI in a real programming language, as there's no programmatic data format like
JSON
/YAML
. Parsing strings from shell scripts is neither safe nor reliable.We fix & patch any & all missing or broken components in any Package we add/build. This means, most soarpkg no longer resemble the "source", wheras AM has a policy that states "it's better to rely on/contribute to upstream, even if upstream has no interest or provides broken packages". You can read, why we disagree: Why not contribute Upstream?
Soar prioritizes Security through its implementation in Rust, a memory-safe programming language. We are committed to maintaining rigorous security standards, including comprehensive Build Logs, robust Checksum validation, and secure build and installation Sandboxes. These protective measures are fundamental to our approach and non-negotiable.
A safer, saner, easier & richer alternative to hacky-shell script was created, it's called
SBUILD
, You can read about it here: https://docs.pkgforge.dev/sbuild/introduction & unless AM ever starts using it, the recipes are entirely incompatible.
Public Tools Search
GitHub Search:
is:public archived:false template:false stars:>5 GUI OR Portable OR Package
(Sorted By:Recently Updated
)
Public Code Search
GitHub Search:
NOT user:Azathothas NOT user:xplshn NOT user:metis-os NOT user:pkgforge NOT user:pkgforge-community NOT user:pkgforge-dev NOT user:pkgforge-security NOT is:fork pkgforge.dev
History & Lore
@Azathothas drafted repos & projects which would eventually become Toolpacks, ~ July, 2023, You can read more about it here: https://docs.pkgforge.dev/orgs/pkgforge-core/projects/toolpacks-bincache/faq#history-and-lore
After Azathothas/Toolpacks#28, PkgCache was created ~ Sep 25, 2024, You can read more about it here: https://docs.pkgforge.dev/orgs/pkgforge-core/projects/pkgcache/faq#history-and-lore
We realized it pretty quickly that, PkgCache wasn't sustainable, and a User Repository consisting of community submitted packages, just like ivan-hc/AM, was desperately needed. Thus, Soarpkgs, came into existence
~ Nov 04, 2024
Last updated