3-May-99 13:06 you wrote:
> Bodo Moeller wrote:
>>
>> On Thu, Apr 29, 1999 at 03:10:55PM -0400, David Harris wrote:
>>
>> > My original request was for something slightly different, I think.
>>
>> > Let me explain what I want to do exactly.... I want to run "make" and have
>> > all the programs compiled _as-if_ they would be installed into the
>> > /usr/local/{bin,lib,include} directories. Then I want to be able to run
>> > "make INSTALL_PREFIX=/tmp/openssl-root/" and have all the files actually
>> > placed into the /tmp/openssl-root/usr/local/{bin,lib,include} directories.
>>
>> O.K., then I'll do this. I don't remember your original message, I
>> just found the reference in the STATUS file ...
> AFAIK (or, have seen) the above wishes for rpm packaging can
> be fulfilled as follows:
> # sh config --prefix=/usr/local --openssldir=/usr/local/openssl \
> [ threads -D_REENTRANT ]
> # make ...
> # make INSTALL_PREFIX=/tmp/openssl-root install
> which leaves the whole installed tree in /tmp/openssl-root with
> the compiled-in paths set to /usr/local/openssl/.. and binaries
> and libraries in /usr/local/{bin,lib,include}.
> To add to the confusion, there is one other common wish for the
> packaging guys: openssl.cnf should not live in a lib/ directory
> because some people want to have that mounted r/o.
> I only have one wish with respect to this: in the above example
> openssl.cnf is installed into /usr/local/openssl/lib/.
> Another config modifier, say --etcdir, to change openssl.cnf,
> and the private/ and certs/ subdirs to be installed there
> should do.
Yes. I'm packager of OpenSSL for KSI-Linux where OpenSSL is system library.
And FHS is very clear here:
1. OpenSSL must go in /usr/lib and NOT in /usr/local/<something>,
OpenSSL programs must be put in /usr/bin and includes in /usr/include or
subdirectory under /usr/include...
("This directory [/usr/local] should always be empty after first
installing a FHS-compliant system. No exceptions to this rule should
be made other than the listed directory stubs.")
2. NO configuration files can be put in /usr
("/usr is the second major section of the filesystem. /usr is shareable,
read-only data. That means that /usr should be shareable between
various hosts running FHS-compliant and should not be written to. Any
information that is host-specific or varies with time is stored
elsewhere.")
3. Configuration files must be put in /etc instead
("/etc contains configuration files and directories that are specific to
the current system. No binaries should be located under /etc.")
4. Plus all files created by running programs (if any) and not intended
for human review must go in /var/cache or /var/state. In /var/cache
there are must be put automatically-restorable data (preformatted man
pages, precompiled TeX .pk-fonts, etc) and in /var/state there are must
be all other variable data not intended for human review...
("/var/cache is intended for cached data from applications. Such data is
locally generated as a result of time-consuming I/O or calculation. The
application must be able to regenerate or restore the data.";
"/var/spool contains data which is awaiting some kind of later
processing. Data in /var/spool represents work to be done in the future
(by a program, user, or administrator); often data is deleted after it
has been processed.";
"The directory [/var/log] contains miscellaneous log files. Most logs
should be written to this directory or an appropriate subdirectory.";
"This [var/state] hierarchy holds state information pertaining to an
application or the system. State information is data that programs modify
while they run, and that pertains to one specific host. Users should
never need to modify files in /var/state to configure a package's operation.
State information is generally used to preserve the condition of an
application (or a group of inter-related applications) between
invocations and between different instances of the same application.
State information should generally remain valid after a reboot, should
not be logging output, and should not be spooled data.")
So yes, --etcdir is highly desirable... Not sure about --vardir -- AFAIK now
automatically generated are only symlinks and looks little exaggerated to have
directory(ies) in /var/state just for symlinks... Still... May be it's not so
crazy idea...
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
