From their GitHub:

cpak installs applications from OCI images while keeping package metadata in a Git repository. It provides native desktop integration, shared content-addressed layers, atomic updates and a rootless Linux sandbox from one Go binary.

It seems interesting. I’ve never heard of it before, but apparently Bottles packages with cpak along with flatpak. The main reason I use flatpaks are its sandboxing capabilities, so it would be cool if cpak brings new stuff to the table while matching or overpassing the sandboxing capabilities.

    • warmaster@lemmy.world
      4·
      1 day ago

      This license provides full access to the source code, encourages public auditing and community collaboration, and imposes copyleft rules. However, because it includes a restriction on replicating the core purpose of the Product, it does not meet the Open Source Definition (OSD) by the Open Source Initiative (OSI), anyway, the point 6b ensures the license will eventually convert to an OSI-approved license.

      FPAL is best described as a source-available, copyleft, and business-protective license.

      Honestly, if any distro included this, it would be an instant red flag.

    • exu@feditown.comEnglish
      2·
      2 days ago

      The restriction pretty much aims at companies like Amazon that rehost an open source project. That sounds pretty fair to me

      • novafunc@discuss.tchncs.de
        1·
        16 hours ago

        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.

      • Elvith Ma'for@feddit.org
        1·
        2 days ago

        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?

        You may not use the Software, in whole or in part, to create, distribute, or operate any product, system, or service whose primary function directly overlaps with or replicates the core business purpose of the Product, unless explicitly authorized in writing by fabricators.

        • Unreliable@lemmy.ml
          1·
          1 day ago

          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.

    • vas@lemmy.ml
      11·
      2 days ago

      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.