asked on

Compile on testbox then move to production

Hi,
Im looking for information on how to compile software on a test box then move it to our production servers. This software would include Apache, PHP, FreeTDS and others. I know how to compile and install all this software, but I want to avoid having to have the compile tools (make etc) on the production servers.
Can anyone tell me how I can compile on a test box, then move the binaries and required files to the production servers.
Thanks!
D.

Tintin

A very common method is to package up the tools using whatever packaging tool you prefer, eg: RPM, YUM, etc. That way you can build in the dependencies and any pre/post install/uninstall steps.

ASKER CERTIFIED SOLUTION

wesly_chen

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

maunded

ASKER

Excellent! So is it safe to assume, that if I, for example, compile Apache without the --prefix switch, that ALL the required files will be in /usr/local/apache2? Will using the prefix switch build a directory structure, that, like PHP for example, puts files in other directorys? Like /usr/lib etc.

wesly_chen

> compile Apache without the --prefix switch, that ALL the required files will be in /usr/local/apache2
As my experience, no.
It will install in /usr/local, not /usr/local/apache2.
You need to specify as --prefix=/usr/local/apache2

> puts files in other directorys? Like /usr/lib etc.
Most of cases, no. They are all under /usr/local/php4....
Only glibc is different, as I know.

maunded

ASKER

Fantastic, thank you very much