> Does anyone want to speak up for the requirement that we continue to support
> BEOS (apparently B/1 and R5?), OS/2, or pre-Windows MSDOS?
Which timeframe do we look at? E.g. if 1.0.2 is released this year and it's
successor
where OS/2 support is removed maybe 2-3 years later (say beginning of 2017),
it's
hard to argue that continuing to support OS/2 is worth the effort with current
commitments on vendor support for that platform ending 2018 (AFAIK).
OTOH, if you're planning on much faster releases, having one more release with
OS/2 support would be nice.
On the third hand, in case it's needed, re-adding os2_rand.c and re-adding about
a dozen "|| defined(OPENSSL_SYS_OS2)" to the cases that will apparently remain
in the code anyway (for the benefit of Win32) doesn't seem like a huge problem
either, so the only real problem would be the build system - mk1mf.pl, mkdef.pl,
libeay.num seem to contain the majority of the references to OS/2 (according to
grep). And if that is getting big changes (see the single makefile thread),
that's
going to be something that needs new work anyway, no matter whether or not OS/2
support was removed from the old build system.
And a question concerning a different platform. Is there any interest in
integrating
"official" support for Windows Phone (old win CE "of course" is something
largely
different...)?
There's a proof-of-concept patch that's rather easily found in the internet
which
has some ugly problems (worst probably being that the random number generator
is not seeded properly). I might be able to (help to) contribute something
better, if
there's interest ...
Regards,
Stefan
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [email protected]
