Appreciate the response! Interesting to read. The Libsodium guys wound up doing exactly what you're suggesting, because of the impossibility of trying to packa

Appreciate the response! Interesting to read. The Libsodium guys wound up doing exactly what you're suggesting, because of the impossibility of trying to package NaCl as-is. So they essentially had to re-do/duplicate all of his build work just to make it packageable. And now there are two competing implementations (three if you count tweetnacl). And a bit of a confusing mess in the documentation department. It seems a little selfish for djb to take the "works on my machine" attitude, because it means that a bunch of other people have to reverse-engineer all that stuff just to make it portable. But I guess OTOH it's his software, so it's his choice. And maybe he doesn't care whether people choose to use his stuff or not, as long as he's publishing.