• LarkinDePark@lemmygrad.ml
    link
    fedilink
    arrow-up
    0
    ·
    3 months ago

    I don’t understand what this has that any other package manager, yum, apt etc doesn’t.

    dependencies stored in their own unique directory

    Yeah so?

    • sus@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      3 months ago

      it’s replicable and “atomic”, which for a well-designed modern package manager shouldn’t be that noticable of a difference, but when it’s applied to an operating system a la nixos, you can (at least in theory) copy your centralized exact configuration to another computer and get an OS that behaves exactly the same and has all the same packages. And backup the system state with only a few dozen kilobytes of config files instead of having to backup the entire hard drive (well, assuming the online infrastructure needed to build it in the first place continues to work as expected), and probably rollback a bad change much easier

      • LarkinDePark@lemmygrad.ml
        link
        fedilink
        arrow-up
        0
        ·
        3 months ago

        you can (at least in theory) copy your centralized exact configuration to another computer and get an OS that behaves exactly the same and has all the same packages.

        As can you with grepping your history of apt commands? And back up that to a file of a few dozen kilobytes too.

        Am I stupid?

        • sus@programming.dev
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          3 months ago

          assuming you have never used anything except apt commands to change the state of your system. (and are fine with doings superfluous changes eg. apt install foo && apt remove foo)