17
Has anyone heard of cpak?
(piefed.world)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
IIRC, it's another brain child of Mirko Brombin; the prolific designer that's also prominently involved with Bottles, Singularity Desktop/OS and Vanilla OS.
I wish it the best. Especially since Flatpak's sandboxing didn't have any competition up till now. At least, AFAIK*.
I just read the license of cpak and I can't say I'm a fan.
Why? It’s a fair license but with corporate restrictions
https://github.com/Containerpak/cpak/commit/92ce3d2c13860199f5e7158cb67b0775957a81de
the linked project literally changed to gpl3 five hours ago.
Honestly, if any distro included this, it would be an instant red flag.
The restriction pretty much aims at companies like Amazon that rehost an open source project. That sounds pretty fair to me
I don't think so, this still would let them host it so long as don't have a "competing fork". I've heard of licenses like Server Side Public License (SSPL) that do you what you say. Basically, that license requires all the infrastructure around the software to be open source to. So something like AWS couldn't host the software without first open sourcing all their infrastructure.
What about this? This basically forbids you to fork the software if you want to - e.g. because they're maybe going closed source in a few years?
The way I read that is they don't want forks fixing specific issues/making improvements when those changes could all be in the one implementation.
Yup, that's simply a deal breaker. [For me].
If it's for you, too, you could maybe even mark the post with [SOLVED] or "Update:...". If you wish. No obligation.