apache not recognized ..?

[bindhaas]

Hi,

I've apache installed and running. Its installed at
/local/apache

startup file is also present at /etc/init.d/apache

Still, the system check dependency suggests

===============================================
2005-08-23 09:23:31,352 ERROR Operation failed: Dependency check failed -- Apache is not installed, it is required by the server
===============================================

what could be the reason for this..?

-bindhaas

[natkins]

Hi bindhass,

What distro are you installing on? I suggest you install the official RPMs of Apache 2.0.x that can be obtained for the distro vendor. The Scalix installer expects to find Apache files in the standard places as it needs to add some configurations.

Cheers,

Nick.

[bindhaas]

Hi,

i've built my own apache with all the relevant fixes and my own modules. Is there a way to make scalix installation accept the prefix to where my apache is installed ..?

-bindhaas

[ScalixSupport]

The installer is expecting the httpd RPM to have been installed, it doesn't go searching for other installations. Presently, there is no way to configure it to check in a different place.

For my own benefit, what distribution are you running on that hasn't provided the latest fixes ?

Cheers

Dave.

[bindhaas]

i generally like to build my own apache, instead of putting a rpm. i suppose part linux community prefers this approach of installing.

i understand your is not an open source but a neatly packaged binary along with a neat installation, but i suggest making this installation configurable so as to adjust to simple things like installation paths, prefix's etc.

is this on your roadmap ?

thanks.

[jch]

This question came up way back when in another place. We had a different installation and configuration program then -- some of the subscribers to this forum will probably still remember it.

Part of the job that the installation program has to do is to verify that the environment that you're trying to install Scalix in is "up to snuff". We need various libraries and whatnot installed (some of which rpm takes care of) and we need some configuration files to be in an expected place (for example, sendmail.cf). While it is possible for support and development to look at a machine and work out whether everything is present and in the right place it is *much* harder for any program. Actually, it becomes a constant battle between the code and scripts and the installation program: changes we make to the server have to be reflected in the installation program. Of course, we do make changes to the installation program as part of development (and that's going on right now as I speak); but in the interests of sanity we want to keep the coupling between the installation program and the rest of the code as loose as possible. Tight coupling just results in something which is unreliable and unmaintainable.

That's the philosophy we adopted then and while we have a very different installation program now, we have a similar philosophy now.

In your particular case, I would recommend adding the patches and whatnot that you need to the Red Hat (or SuSE) RPM and installing that. You'll still be on your own if you have problems relating to the web server, but at least the installer will be happy. And, quite apart from anything else, there are lots of other things that use apache and having the files in the right place and whatnot will make them happier as well.