Jon, et al,
I concur with what you're saying about mucking with core OS
directory structures, except for maybe certain things within /etc.,
and the concept of moving from /usr/local (BSD derived) to /opt
(System V derived). For all practical purposes, I think
of /opt as /usr/local only more for the enterprise (exportable).
Probably from time I spent at Bell Labs. Enough on philosophy.
My reasoning for the hierarchy is derived from the way Debian
by default installs Apache. That is the directory structure I
gave to you. I figured I'd keep the configs, mods, logs, etc.
where dpgk put them, (/etc/apache, /usr/lib/apache, /var/log/apache,
etc.), and move the executable stuff to my perceived equivalent
to your /usr/local, (that being /opt). Perhaps not necessary,
but the ability to do so is one of the beauties of a powerful
OS like Unix. I don't know how familiar you are with Debian,
but from what I've seen, it more closely resembles system V
than any of the other distributions. Come to think of it, I'm not
even sure Debian creates /usr/local by default during install.
Doesn't create /opt either come to think of it ;-)
Anyway, Apache's config.layout accommodated me rather well
once I realized it was available. Until that time I was trying to build
a script with all the absolute paths set as arguments. Damn near
impossible. JServ attempts to do that much the same way, that
is set paths with arguments. Problem is there is no way that I can
tell to override that some of them are relative to --prefix. I
did see after ./configure that I could probably go directly into the
makefile and modify the paths there, but I decided not to take that
risk and sort things out manually after the fact.
What I would like to see is something exactly like config.layout
in the Apache distribution. That is, if I so choose, to override
default and relative paths. Matter of fact, it might be simple
enough to expand the parameters of configure.options to accommodate
absolute paths. Not that I'd stop using JServ if I weren't
accommodated. I know what I like
Maybe there is an alternative for me. That is to get to petition Debian
to include JServ in the distribution. That way at least it would be
installed
to work in a default configuration.
Jack
jon * wrote:
> hmmm...i'm not quite sure what you are asking for, but i for one totally
> disagree with your choice of installation directories because i have been
> brought up to believe that stuff that isn't core OS shouldn't reside within
> anything other than a /usr/local directory structure. of course i abstract
> that out with a model like what GNU stow produces (i have some custom perl
> scripts that work quite like stow that i have been using for about 5-6 years
> now).
>
> so, could you please detail how exactly you would like to see apache jserv
> change in such a way to reflect your installation?
-- --------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
