Robert Joop wrote:
> some packages, apache httpd for example, default to differ from this layout
> and put all their stuff into a directory of their own, e.g.
> /usr/local/apache/{bin,conf,logs,...}
>
> since openca is not command line based, we haven't got much to put into
> ../bin/ (one users got in their $PATH), so perhaps openca is similar
> to apache?
Having all the files within the same directory allows for very simple
"removal" of the package from the system as you always get the /usr/local/bin
ever growing and, if not using a package manager (rpm, pkg, etc...)
you almost certainly will live with unused binaries in the system...
> so what are the fs layouts we want openca to fit in?
I would like to have openca to respect the default layout as much as
possible, anyway with the possibility to prefix them with, let's
say, the default "openca" -- just as apache, openssl and other
packages.
> the current ./configure defaults are not standard, at least not the
> /home/httpd/, where does that come from?
It is historical. This was my installation directory for htdocs and
web stuff as the /home partition is usually big, also having the directory
of the user the server web runs as it was not a bad idea...
This could be changed, anyway.
> i would like to see openca configurable with very few options, perhaps
> even none concerning paths, while on the other hand offer the
> opportunity to fine tune it to strange systems.
I am with you.
--
C'you,
Massimiliano Pala
--o-------------------------------------------------------------------------
Massimiliano Pala [OpenCA Project Manager] [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.openca.org Tel.: +39 (0)59 270 094
http://openca.sourceforge.net Mobile: +39 (0)347 7222 365
S/MIME Cryptographic Signature
