I would like the package to be working for Pharo. Now from your description I have problem to really understand the situation. I think that Pharo core should have minimum and packages should be able to be loaded nicely on top.
> Currently, SHA1, SHA256 and MD5 all get redefined by Cryptography-zzz.111.mcz > loading. Do you mean that the version in Pharo are older than the one in 111? Stef On Tue, Oct 24, 2017 at 6:17 PM, henry <[email protected]> wrote: > I am curious as to integration of the newest Cryptography package there into > Pharo. There are two Undeclared: SoundRecorder and FillInTheBlank, though I > do not know if such would be a part of a Pharo-Squeak compatibility layer. > > More pertinent would be what to do with the HashFunctions that already > reside in the Pharo image. If the decision was to include the entire > Cryptography into base, then making the HashFunctions not go Obselete would > be the objective. > > Currently, SHA1, SHA256 and MD5 all get redefined by > Cryptography-zzz.111.mcz loading. > > What do you think about bringing Cryptography up to date for Pharo and what > would be needed. It would help to seek common ground between Squeak and > Pharo, yes? > > > - HH > >
