In the current live version of Pacstall, the PacScript specification allows for various types of dependencies (runtime, build, optional). This strategy works well for packages published within the same distribution, such as Ubuntu 23.04. However, it has been proven multiple times that it doesn't work effectively when dealing with multiple distributions that package different versions of base packages (e.g., openssl, nodejs, go).
Let's consider a hypothetical PacScript example: Imagine a person wants to distribute their new GUI application written in Go. They discover Pacstall and decide it's the best way to distribute packages on Debian-based distributions. After quickly learning the syntax for the PacScript file, they fill in the name, description, download link, and a single dependency: Go (the programming language). They test it locally using the Pacstall Org. tooling, and it works perfectly. Satisfied, they publish it t