FAQ

Frequently Asked Questions & Misc

Why not contribute Upstream?

  1. Unfortunately, with the mass adoption of Flatpaks, most developers have no interest in AppImages or other formats

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

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

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

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

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

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

  5. The reasons, listed above, make PkgForge's & AM's philosophy & goals incompatible for a direct collaboration.



  • 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

  • Google|Bing|Baidu: "*pkgforge.dev" -site:pkgforge.dev -site:ajam.dev


History & Lore

Last updated