• Telorand@reddthat.com
    link
    fedilink
    English
    arrow-up
    4
    ·
    3 months ago

    I watched a couple of keynotes about it, and bootc is better, tbh. Bootable containers is definitely the way to go, and I’m excited for when it’s released to the public (officially, it’s still available to download in the meantime).

    I’ve been trying to get a weird VPN package installed that has to be installed to the system layer, but you have to run it as a user. Since containers are mutable, it should be trivial to install it. The main problem with rpm-ostree is that, as great as it is, it only works with RPM files, and sometimes you need to run something that doesn’t have an RPM option.

    • boredsquirrel@slrpnk.net
      link
      fedilink
      English
      arrow-up
      3
      ·
      3 months ago

      Yes packaging RPMs for random little things is annoying, but not an unsolvable issue.

      I think there is a tool to make RPMs from directory structures, but I also never built an RPM.

      sddm2rpm is a good example of such a hack.

      • Telorand@reddthat.com
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 months ago

        I’ve tried looking up guides, and it’s not a simple task, especially if you’re reverse engineering somebody else’s script. If I can just run it in a bootable container as if I was using a typical mutable system, that’s something pretty much everybody can do.

        But I agree, there’s a few tools that make building RPMs and flatpaks easier, and it can be done. It’s just that the learning curve is steeper, and that is going to keep certain people away from immutable distros.