• Chewy@discuss.tchncs.de
    link
    fedilink
    arrow-up
    39
    arrow-down
    2
    ·
    1 year ago

    Yes, but each package manager has it’s (dis-)advantages. It’s great to have flatpak and docker to be able to run software on almost all distros, but the OS still needs a way to update.

    Almost all immutable distros use multiple package manager.

    • Fedora Silverblue: rpm-ostree + flatpak (+ toolbox)
    • OpenSUSE MicroOS: zypper with snapshots (transactional-update) + flatpak (+ distrobox)
    • NixOS is unique since it only uses the Nix package manager
    • immutable Ubuntu will probably only use snap for OS + apps.

    All those OS support distrobox and docker additionally.

    • monk@lemmy.unboiled.info
      link
      fedilink
      arrow-up
      17
      ·
      1 year ago

      NixOS is unique because it uses the only potent package manager (if we don’t count that one reimplementation of Nix). Calling the others “package managers” becomes mostly a courtesy when NixOS enters the picture.

      lalala with FS-level snapshots + flatpak + distrobox + a kitchen sink

      look_what_they_need_to_mimic_the_fraction_of_our_power.png

      • GuybrushThreepwo0d@programming.dev
        link
        fedilink
        arrow-up
        14
        ·
        1 year ago

        I don’t consider myself a dumb person but I couldn’t figure out nix when last I decided to play with it. Theoretically it seems super interesting to me, but I really just can’t dedicate the time again now to learn that esoteric syntax.

        • Chewy@discuss.tchncs.de
          link
          fedilink
          arrow-up
          16
          ·
          1 year ago

          The docs for NixOS aren’t good. Much knowledge is on many blogs but who knows them all?

          Having the OS defined declaratively is great but I also dislike the Nix language.

          Once it’s setup NixOS is great. Sharing configs with PC and laptop is awesome. Rollbacks are baked in.

          Going off the https://github.com/Misterio77/nix-starter-configs helped me gettung started.

          • silicon_reverie@lemmy.world
            link
            fedilink
            arrow-up
            7
            ·
            edit-2
            1 year ago

            I absolutely loved NixOS on paper, and it’s undoubtedly the best way to combat updates that break my dependency trees, but I still found myself spending a majority of my time attempting to hard-code various app configuration files into my convoluted configuration.nix with its esoteric syntax rather than actually using my computer. Am I missing something, or does a good install script covering my favorite packages and a git bare repo storing my dot-files get me 90% of the way there without the hassle of bending my whole OS around a single nix config monstrosity?

            • Chewy@discuss.tchncs.de
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              Agreed, I’m also considering switching to an install script + btrfs snapshots. It worked quite well a few years ago, altough it doesn’t solve configuration drift.

        • monk@lemmy.unboiled.info
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          The syntax is just the outer layer, the whole concept inside it is alien. It’s like a smartphone for a person who’s only seen books.

    • merthyr1831@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      1 year ago

      all the more reason to sunlight these old packaging formats and move to universal solutions like flatpak and nix