If that was your problem, you should've said so instead of spinning it up into an entirely different security problem that plainly did not exist.
> Thanks for suggestion. I did exactly that
Except you didn't stop spreading falsehoods. You've spent more lines using your brand new HN account spreading lies about an open source project people have dedicated their free time into.
> professionally work with Erlang, and I know what is hack and what is not.
Fixating on hyper specific implementation details taken out of context without considering the design, intent, and usage is not what I call professionalism in the software industry.
> Language-specific packaging should be left to language-specific package managers, they have more domain knowledge.
Domain knowledge that fails to build or run portably even on widely used FHS-compliant Linux distros.
> Nix doesn't solve this dilemma in any better way.
I've already explained about the problems distro package maintainer faces and how Nix alleviates some of the problems which you then responded with a totally unrelated "Docker exists" nonsense.
> Take systems software from the distro-provided packages, add my own stuff on top.
So packaging problems won't exist if we just stick with Docker, but you would use distro packages to create a Docker image? How would that even work?
> Building RPM is a nobrainer.
Go tell that to RedHat maintainers.
> Please take a closer look at what you're quoting. You missed a very important part: > > (or its analogue in /nix)
/etc in NixOS is not /nix. It's /etc. Very important indeed.
> You see, if I want to utilize Nix to full extend and use its main "reproducibility" feature, I need to put all my configuration in a derivation. Configuration includes secrets. Derivations are world-readable.
You see, Please. Stop. Repeating. Lies.
You don't put secrets in a world-readable location, period. The typical Nix way of handling secrets is that you store in them in a secure path and point the configuration to that path.
> Distros maybe don't, but "bug-ridden kludge that is Ansible" (according to Nix user) does.
You can use numerous solutions that can work together with Nix. How about NixOps, which, among other things, handles secrets management? Or what about, say, Ansible? After all, any solution that would be able to send the Nix configuration, place secrets in a secure filesystem path, and run commands to build the Nix configuration would suffice.