(This comment by Eric Siegerman <[EMAIL PROTECTED]>, logged in as "guest".)

[levitte - Fri May  7 16:06:59 2004]:
> As far as I understand things (I didn't define this, so I can only say
> what I observed), machine-dependent things are placed in
> $(INSTALLTOP),
> while machine-independent things are placed in $(OPENSSLDIR).  The
> latter involves a few scripts as well.

That doesn't look to me like the intended criterion.  After all, 
.h files go in $(INSTALLTOP).

It looks to me as though the goal, if --prefix=/usr/local is
specified, is to do a typical UNIX installation, where files go
in their standard locations under /usr/local/bin,
/usr/local/include, and so on.  That way, people don't have to
have to add entries to their various search paths (environment
variables, but also -I and -L lists in builds) to pick up the
OpenSSL stuff.  Anything that doesn't have an obvious standard
location goes under /usr/local/ssl, presumably in order to reduce
pollution of the /usr/local directory itself.

As things currently stand, the only exception to the above rule
is the man pages; after a --prefix installation, the *only*
search path a user needs to modify is MANPATH.

Thus, if I'm correct about the goal of --prefix installations,
then in order to satisfy that goal, "man" does indeed need go
under $(INSTALLTOP).

(In the absence of a --prefix option, the idea clearly seems to
be to isolate the entire package under $(OPENSSLDIR); this case
appears irrelevent to the current discussion.)
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to