bio

  • 25 Posts
  • 35 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle
































  • That seems like an argument for maintaining a frozen repo of packages, not against containers.

    I am not arguing against containers, I am arguing that nix is more reproducible. Containers can be used with nix and are useful in other ways.

    an argument for maintaining a frozen repo of packages

    This is essentially what nix does. In addition it verifies that the packages are identical to the packages specified in your flake.nix file.

    You can only have a truly fully-reproducible build environment if you setup your toolchain to keep copies of every piece of external software so that you can do hermetic builds.

    This is essentially what Nix does, except Nix verifies the external software is the same with checksums. It also does hermetic builds.





  • Are you saying that nix will cache all the dependencies within itself/its “container,” or whatever its container replacement would be called?

    Yep, sort of.

    It saves each version of your dependencies to the /nix/store folder with a checksum prefixing the program name. For example you might have the following Firefox programs

    /nix/store/l7ih0zcw2csi880kfcq37lnl295r44pj-firefox-100.0.2
    /nix/store/cm1bdi4hp8g8ic5jxqjhzmm7gl3a6c46-firefox-108.0.1
    /nix/store/rfr0n62z21ymi0ljj04qw2d7fgy2ckrq-firefox-114.0.1
    

    Because of this you can largely avoid dependency conflicts. For example a program A could depend on /nix/store/cm1bdi4hp8g8ic5jxqjhzmm7gl3a6c46-firefox-108.0.1 and a program B could depend on /nix/store/rfr0n62z21ymi0ljj04qw2d7fgy2ckrq-firefox-114.0.1 and both programs would work as both have dependencies satisfied. AFAIK using other build systems you would have to break program A or program B (or find versions of program A and program B where both dependencies are satisfied).