Wouldn't it be better to make multithreaded the default? That is what
the old script does, doesn't it?
__
OpenSSL Project http://www.openssl.org
Development Mailing List
special case. It'll have to be pretty severe to justify breaking the entire
existing code base.
How about keeping symlinks in place for a transition period? Then old
applications can be built unmodified, but if a name conflict occurs
the user can simply rm -f include/*.h
After some time
On Fri, Apr 23, 1999 at 02:21:12AM +0200, Bodo Moeller wrote:
[...] Now whether /usr/local/include/openssl is a link or a
directory with copies of all the files doesn't really make a
difference, what counts is that the name-space makes sense.
Since there seems to be mostly agreement to the
I'll commit the appropriate changes tonight unless somone vetoes very
quickly. In addition to the actual #includes, many Makefile.ssl's
need a tiny change, Makefile.org needs a couple of tiny changes; so
does mk1mf.pl (I verified building the changed library with
Und OPENSSL_VERSION_NUMBER
Oops. I didn't mean to send that to the list (and it is wrong, too--in
order to check the version header you'd have to find it first.)
__
OpenSSL Project http://www.openssl.org
Development Mailing
-BEGIN PGP SIGNED MESSAGE-
At 16:29 23.04.99 +0200, you wrote:
Since there seems to be mostly agreement to the change to
openssl/*.h (including a "Yes, please!!!" sent via private mail -
:),
I'll commit the appropriate changes tonight unless somone vetoes
very
quickly. In addition to
An issue that still is open as of yet is what to do with the exported
header files. Currently, /usr/local/ssl/include/foo.h will
#include "bar.h"
which it should't --
#include bar.h
is better because it cannot conflict with application files.
However, I'd prefer moving everything to
Bodo Moeller wrote:
An issue that still is open as of yet is what to do with the exported
header files. Currently, /usr/local/ssl/include/foo.h will
#include "bar.h"
which it should't --
#include bar.h
is better because it cannot conflict with application files.
However, I'd prefer
On Thu, Apr 22, 1999 at 07:30:15PM +0200, Anonymous wrote:
[...]
Moving everything to /usr/local/ssl/include/openssl doesn't make much sense
though.
- That will leave /usr/local/ssl/include empty except for the subdir.
True, but that shouldn't hurt anyone. It's just another inode.
-
Bodo Moeller [EMAIL PROTECTED] wrote:
On Thu, Apr 22, 1999 at 07:30:15PM +0200, Anonymous wrote:
[...]
- That will leave /usr/local/ssl/include empty except for the subdir.
True, but that shouldn't hurt anyone. It's just another inode.
No, it doesn't hurt. It's just silly.
-
10 matches
Mail list logo
