-
build-scripts
All-in-One build/compile scripts repository that aims to simplify the process of manual compilation/installation via automated shellscripts (by Thanatisia)
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
warzone2100
Command the forces of The Project in a battle to rebuild the world after mankind has been nearly destroyed by nuclear missiles. A 100% free and open source real-time strategy game for Windows, macOS, Linux, BSD+
This is the repository build scripts repository
What is the server code other than "something that distributes a .snap file"? Given that I can, if I want, take a .snap file to an airgapped machine and install it, it appears pretty trivial to offer alternatives to Canonical's infrastructure if anyone were particularly interested.
Personally, having created my own Frankendebian and having dealt with similar namespace collision hell on Red Hat, Fedora, and even with Flatpak, I understand why snapd restricts a machine to a single repository at a time. The good news is that if you don't like that, you can always fork it and change it - something you don't have the luxury of doing with things like Google Play...
Oh right, I'd forgotten that with Flatpak you don't get convenient things like being able to type the executable name or a directory in $PATH. And their workaround for namespace collisions is to just mandate excessive verbosity unfailingly. Not sure I like this solution, nor the aggressive responses from some of the Flatpak developers when people asked for a solution.
And if they do happen to be going to a specific app's website, it's not like they can't get a snap link from the developer.
So you want another way to distribute the packages? Such as wrapping the snap file in an rpm like I mentioned earlier? You could even set up appstream metadata for it. But that still doesn't solve the problem of one source getting too much power - just like flatpak doesn't solve that problem.