On Fri, 2002-03-15 at 12:23, zentara wrote:
If you want to comply with suse's method, you probably should use their "source rpms" for each package. It comes with the configuration files usually set.
Yeah, I know, but obviously, they're not going to have _every_ package out there. They're definitely not going to have the latest and greatest package versions in most cases, nor will the SuSE RPMs be compiled with all the features you may want. Hence -- the installation from source!
However, their is nothing from stopping you from installing the source from apache in their default directories. You can have 2 different versions of apache running. You just have to read the docs and remember which config file goes with which httpd daemon.
I know I can install in the default directories, but I'd rather install where I don't have to make 16K adjustments to the init-scripts or whatever to make the system work. When I installed qmail I was able to install via a tutorial, and it was a very well-thought-out tutorial. It had you create the install directory your self as well as several directories inside it, the catch being, these internal directories were actually symlinks from other places on the machine. (i.e. /var/qmail/control actually = /etc/qmail -- this way you can edit any of the configs from /etc/) :) Pretty clever idea! If any distro would do that with the packages, it would serve to explain a layout for future package installs much easier. (i.e. install package xxx in /usr/local/xxx then link the relative info to /usr/bin /usr/man /etc/xxx and so on) My 2 cents on File System structure. T.