Due to the nit picky dependencies and required compiler options of all
the various components, IMHO the best way to handle this is to download
and compile all the various bits and pieces and installed them in a
local tree (such as /usr/local.) When I say “all the bits and pieces”,
I’m referring to perl, apache, mod_perl, and all the perl modules. You
might get away with the version of MySQL that comes with the OS however.
I haven’t tried it yet myself, but RH9 should work with the stock
programs if you install RT3 to run under fastcgi instead of
mod_perl. RH7.3 should also work with a copy of perl 5.8.x
compiled in /usr/local/ and used for fastcgi execution. You
want the latest rpm updates of course, and perl modules from
CPAN. Mysql or postgres can be replaced with newer releases
with available RPMs.
It seems like a large task (and IS to a certain extent) but it’s well
worth it in the long run. You are creating a stable environment so that
it’s MUCH less likely that OS changes / upgrades will break your RT
environment. If you are creating a production installation, this is what
I would recommend.
On the flip side doing that means you will have to repeat the process
for every update to perl, apache, mod_perl, etc. instead of just
running up2date, apt-get, yum, or whatever handy method is
available for stock system programs.
Les Mikesell
les@futuresource.com