In message <09111210562552_20202...@antinode.info> on Thu, 12 Nov 2009 10:56:25
-0600 (CST), "Steven M. Schweda" <s...@antinode.info> said:
sms> From: "Dr. Stephen Henson" <st...@openssl.org>
sms>
sms> > Can you (and others in this thread) please submit bug fix patches to the
sms> > request tracker (r...@openssl.org) so they don't get overlooked??
sms>
sms> From my point of view, "overlooked" is less of a problem than
sms> "rejected". And some of the stuff which gets added appears to
sms> have been tested by no one.
I call it "priorities", so some things aren't permanently rejected,
just have lower importance in my view (and I do take on a role as peer
reviewer, hope you don't mind). The main reason to do so is that I
want to have as little sources of error in my build as possible, so I
take in one piece at a time.
sms> Obviated the annoying copying of C source files into the
sms> "test" directory (symlinks being unsupported on many VMS systems
sms> and/or file systems).
While annoying, it's not something that stops the build from working,
ergo lower priority.
sms> Added an "SSL_" prefix to the object library names so that a
sms> victim might have some chance of identifying the things amid the
sms> clutter in SYS$SHARE:
Most victims have read some documentation and therefore know what the
library names are. Also, the names mimic the Unixly names, so those
coming from there will immediately recognise them. And not the least,
it would affect the victims, as you pointed out yourself. Ergo, lower
priority.
sms> I also tried building the stuff before I submitted my
sms> suggestions.
I've another construction with a nightly build that fetches the latest
snapshot and tries to build it. Not optimum and means some commits
will contain errors, but when my time is short, that's the best I can
do.
sms> Some of these proposed changes involve functional changes
sms> which would affect the victims (object library and shared image
sms> file name changes, for example), so deserve some discussion. I
sms> see very little such discussion here. Suggestions get submitted.
sms> Some get adopted. Some get rejected. I find out what happened
sms> when I see the next "betaN" kit. It's not very satisfying, and
sms> I've largely stopped caring. (This may or may not be seen as
sms> much of a loss.)
We're automatically building nightly source snapshots, maybe you
should have a look at those.
Now, for my own shit to admit, I haven't looked at this for a couple
of months, and it weighs on me. There are other things in life that
have preoccupied me a little too much, and I have overlooked OpenSSL.
I'm trying to get back on track as we speak, and I'll try to find time
to spend so my testing cycle gets a bit faster than "try one change
per night"...
Cheers,
Richard
--
Richard Levitte rich...@levitte.org
http://richard.levitte.org/
"Life is a tremendous celebration - and I'm invited!"
-- from a friend's blog, translated from Swedish
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
