Learning about Nix OS

Apparently it figures out which packages are ongoing dependencies for something by scanning all of its result files for nix package paths or nix hashes. Things are pretty much never explicitly declared as runtime dependencies, it's just assumed that if the reference is there, it uses it.

I'm feeling very uncomfortable but I'm unable to argue that something is definitely wrong so I am remaining in the room

· · Web · 0 · 0 · 1
Sign in to participate in the conversation

Merveilles is a community project aimed at the establishment of new ways of speaking, seeing and organizing information — A culture that seeks augmentation through the arts of engineering and design. A warm welcome to any like-minded people who feel these ideals resonate with them.