X-Git-Url: https://git.openssl.org/?p=openssl.git;a=blobdiff_plain;f=STATUS;h=e7b7687272249d92f54a07fd480fd7883f63f6e9;hp=393fb66b92daa052becca998085a54f73a5b2a51;hb=b6cff93dcf510d473c5da93227f06366ed7638a9;hpb=a6f20a1e0173f1309074c3175928eeb6ded28244 diff --git a/STATUS b/STATUS index 393fb66b92..e7b7687272 100644 --- a/STATUS +++ b/STATUS @@ -1,6 +1,6 @@ OpenSSL STATUS Last modified at - ______________ $Date: 1998/12/31 12:14:27 $ + ______________ $Date: 1999/01/21 13:01:20 $ DEVELOPMENT STATE @@ -19,6 +19,34 @@ OPEN ISSUES + o The Makefile hierarchy and build mechanism is still not a round thing: + + 1. The config vs. Configure scripts + It's the same nasty situation as for Apache with APACI vs. + src/Configure. It confuses. + Suggestion: Merge Configure and config into a single configure + script with a Autoconf style interface ;-) and remove + Configure and config. Or even let us use GNU Autoconf + itself. Then we can avoid a lot of those platform checks + which are currently in Configure. + + 2. The massive symlinking of Makefile.ssl -> Makefile: + First the `make -f Makefile.ssl links' command is nasty, second the + whole process is slow and third it seems to be done without real + need. And forth, the dependecies are currently missing. And fifth, + it's complicated to always go to the top-level in order to get the + local variables overriden. + Suggestion: Rename Makefile.ssl to Makefile.in, add + dependencies to Makefile.in and change the build process + to _generate_ Makefile out of Makefile.in by + substituting variables like CC, etc. This solves the + above problems. + + 3. The xxx.org -> xxx.h generation: + It's not obvious for which file xxx.org is the source. + Suggestion: Rename xxx.org to xxx.h.in (Autoconf style), this way + one sees that xxx.h.in is the input for xxx.h + o The installation under "make install" produces a very installation layout: $prefix/certs and $prefix/private dirs. That's not nice. Ralf suggests to move the two certs and private dirs either @@ -28,6 +56,14 @@ Status: Ralf +1 for both not installing the certs at all and moving it to $prefix/etc/. +0 for $prefix/lib/ and $prefix/share. + Paul: why is it not nice? + Ralf: because it messes up the install dir when + $prefix is not a dedicated area like /usr/local/ssl. + When we move them to a standard subdir like + etc/ lib/ or share/ we don't mess up things + when $prefix is /usr or /usr/local, etc. + Additionally it makes package vendors life + easier.... o Support for Shared Libraries has to be added at least for the major Unix platforms. The details we can rip from the stuff @@ -51,6 +87,7 @@ Status: Ralf thinks we should both contact the author of Net::SSLeay and look how much effort it is to bring Eric's perl/ stuff up to date. + Paul +1 o Ralf has ported Stephen's pkcs12 program to OpenSSL (the ASN.1 stuff Eric recently changed :-( ), but needs some help from @@ -60,6 +97,19 @@ thinks pkcs12 should be incorporated better now than later because it's nasty to not have it in the core - one always has to install it manually and a lot of people use it. So, should we incorporate it? + BTW, we have to be carefully because of the pkcs12 license: There are + some things which don't match the OpenSSL license, so Stephen has to + change it for us when we want to incorporate the code. Status: Ralf +1, Stephen -0 - + + WISHES + + o Damien Miller: + "How about making the each of the locations compile-time defined. I + would like to (for example) put binaries in /usr/bin, configuration + data, certs and keys in /etc/openssl/certs and /etc/openssl/keys, etc. + This would also be a great boon to binary package makers. The + SSLeay-0.9.1b RPM already includes some patches which do some of this. + I can forward them if you wish." +