heikki at OSAFOUNDATION.ORG
Tue Jun 14 19:26:51 CEST 2005
Thomas D. Uram wrote:
> Okay, the type mapping problem I was having is resolved by using swig 1.3.24 with latest
> m2crypto (from subversion). The following two issues remain:
> - The build still requires the inclusion of compile.h as I indicated earlier in this thread.
Ok, filed as https://bugzilla.osafoundation.org/show_bug.cgi?id=3258
> - swig 1.3.24 emits many deprecation warnings (complaining that %name has changed to %rename)
Yes, this is known. I'd like to keep it as it is until %name won't be
supported anymore, and then bump the required swig version number
> So, it looks like I would want to use the development code instead of the 0.13 release.
> Is there a timeline for the next release?
I haven't heard from Ng in a while, but I plan to make a first release
candidate during the M2Crypto sprint in Europython in three weeks or so.
I'd like to use similar process as OpenSSL does, to gather reports of
successful builds, regressions, problems etc. and then do the actual
release when things seem good.
I will go on vacation after Europython, so unless Ng picks things up,
the release probably won't happen until late July the earliest.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 249 bytes
Desc: OpenPGP digital signature
More information about the python-crypto