If you mean distributions with sourcetree, I don't agree that not having nettle in then is a good idea.
The Crypto/SSL parts of pike are rather central to it as it is.
Not always having hash/randomization/crypto functions available is not a good idea, as an example it would not be possible to write something like bittorrent in pike.
/ Per Hedbor ()
Previous text:
2003-03-11 22:44: Subject: nettle-1.7
Blame on me. I should have gone English. The topic is how-to-replace-Crypto-with-Nettle.
jhs or some pelix root can fix an account for you.
I don't remember anything you wrote about a Pike Nettle interface, but I've not had any major problems with the current one. The current interface, but with Capitalized programs and a move from update/digest to feed/drain would satisfy me.
I agree that not having Nettle in the source tree could be a good idea, if we post enough pointers to where to find it (e.g. putting releases on the Pike ftp). As long as changes can be countered by configure scripts I don't see that there is a problem with incompatible changes in Nettle.
/ Martin Nilsson (har bott i google)