Choice of platform

Hi,

I have been tested RT for 2-3 months and want to put it in production.
I made the tests on Fedora Core 2 which comes with perl >= 5.8.3.
Works well.

Now our preferred platform is Scientific Linux 3.02 which is based on
RedHat Enterprise Linux RHEL3 update 2. I could also use the new version
based on RHEL3 update 3.

The problem is that perl on RHEL3 is 5.8.0. I tried to upgrade it by
rebuilding Fedora Core 2 perl SRPMS packages on SL.
I came accross many problems (mod_perl not working, etc…). The whole
thing seems unstable now.

I have several possibilities now and I am asking for advice :

a) Re-install Scientific Linux without perl if possible and add
perl an mod_perl later based on FC2 SRPMS packages like I did.
This is mostly what I tried already but starting without perl installed.
But I am afraid this could cause problems later when updating
packages…

b) Use a Fedora Core 2 platform like I did. I need an additional
machine for RT only because this platform cannot be shared with
other applications I have on SL.

c) Use RPM packages for RHEL. Theses packages are RT V3.0.10-3.
Here, the question is : what are the differences between RT 3.2
(tarball edition) and RT 3.0.10-3 in theses packages ?

Thanks.

Jean-Michel BARBET.

Jean-michel BARBET | Tel: +33 (0)2 51 85 84 86
Laboratoire SUBATECH Nantes France | Fax: +33 (0)2 51 85 84 79
CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: barbet@subatech.in2p3.fr

Hi,

[…]

c) Use RPM packages for RHEL. Theses packages are RT V3.0.10-3.
Here, the question is : what are the differences between RT 3.2
(tarball edition) and RT 3.0.10-3 in theses packages ?

d) Put your RT in something like /opt/rt and a dedicated self compiled
perl in /opt/rt/perl

That’s what I did on Debian Woody :wink:

Emmanuel Lacour ------------------------------------ Easter-eggs
44-46 rue de l’Ouest - 75014 Paris - France - M�tro Gait�
Phone: +33 (0) 1 43 35 00 37 - Fax: +33 (0) 1 41 35 00 76
mailto:elacour@easter-eggs.com - http://www.easter-eggs.com

Emmanuel Lacour elacour@easter-eggs.com writes:

d) Put your RT in something like /opt/rt and a dedicated self compiled
perl in /opt/rt/perl

That’s what I did on Debian Woody :wink:

That’s my approach, too. RT has so many perl dependencies that I prefer
to give it its own perl installation to play with…

Leif Nixon Systems expert
National Supercomputer Centre Linkoping University

Leif Nixon wrote:

Emmanuel Lacour elacour@easter-eggs.com writes:

d) Put your RT in something like /opt/rt and a dedicated self compiled
perl in /opt/rt/perl

That’s what I did on Debian Woody :wink:

That’s my approach, too. RT has so many perl dependencies that I prefer
to give it its own perl installation to play with…

Thanks to you both,

In this case, I suppose the modules downloaded and compiled from
CPAN with the fixdeps script would go in the /opt/rt/perl hierarchy.
Right ?

JM

Jean-michel BARBET | Tel: +33 (0)2 51 85 84 86
Laboratoire SUBATECH Nantes France | Fax: +33 (0)2 51 85 84 79
CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: barbet@subatech.in2p3.fr

Right, and that will happen automatically if fixdeps is using
the right perl.On Mon, Dec 06, 2004 at 01:57:47PM +0100, Jean-Michel Barbet wrote:

Leif Nixon wrote:

Emmanuel Lacour elacour@easter-eggs.com writes:

d) Put your RT in something like /opt/rt and a dedicated self compiled
perl in /opt/rt/perl

That’s what I did on Debian Woody :wink:

That’s my approach, too. RT has so many perl dependencies that I prefer
to give it its own perl installation to play with…

Thanks to you both,

In this case, I suppose the modules downloaded and compiled from
CPAN with the fixdeps script would go in the /opt/rt/perl hierarchy.
Right ?

JM

Jean-michel BARBET | Tel: +33 (0)2 51 85 84 86
Laboratoire SUBATECH Nantes France | Fax: +33 (0)2 51 85 84 79
CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: barbet@subatech.in2p3.fr


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT wiki at http://wiki.bestpractical.com

b) Use a Fedora Core 2 platform like I did. I need an additional
machine for RT only because this platform cannot be shared with
other applications I have on SL.

That’s the easiest, of course. especially if you already have the
box. You could put the sql server elsewhere if the RT box does not
have a good disk system.

or
d) Compile your own perl for RT, but switch to fastcgi so you don’t have
to deal with rebuilding apache/mod_perl and installing all the Apache::
modules.

Les Mikesell
les@futuresource.com

Leif Nixon wrote:

That’s my approach, too. RT has so many perl dependencies that I prefer
to give it its own perl installation to play with…

Thanks to everybody. I compiled perl 5.8.3 on Scientific Linux 3.03
(RedHat EL3 update 3 actually). Now I am fighting hard with mod_perl
which refuses to rebuild.

I found a first bug here :
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=108769

Now it still refuses to build because it looks for a path
with ‘vendor_perl’ when creating the binary RPM from the built
root. I suspect this ‘vendor_perl’ has to see with the way I
compiled perl itself…

I find it hard and I am still considering other options like having
a separate Fedora Core 2 machine for RT or using the RPMs provided
for RHEL. I am still wondering how different RT3.10 is from RT3.2…

Jean-Michel BARBET.

Jean-michel BARBET | Tel: +33 (0)2 51 85 84 86
Laboratoire SUBATECH Nantes France | Fax: +33 (0)2 51 85 84 79
CNRS-IN2P3/Ecole des Mines/Universite | E-Mail: barbet@subatech.in2p3.fr

Leif Nixon wrote:

Thanks to everybody. I compiled perl 5.8.3 on Scientific Linux 3.03
(RedHat EL3 update 3 actually). Now I am fighting hard with mod_perl
which refuses to rebuild.

Why not using fastcgi, in my experiences, it’s as fast as mod_perl.

Emmanuel Lacour ------------------------------------ Easter-eggs
44-46 rue de l’Ouest - 75014 Paris - France - M�tro Gait�
Phone: +33 (0) 1 43 35 00 37 - Fax: +33 (0) 1 41 35 00 76
mailto:elacour@easter-eggs.com - http://www.easter-eggs.com

Thanks to everybody. I compiled perl 5.8.3 on Scientific Linux 3.03
(RedHat EL3 update 3 actually). Now I am fighting hard with mod_perl
which refuses to rebuild.

[…]

I find it hard and I am still considering other options like having
a separate Fedora Core 2 machine for RT or using the RPMs provided
for RHEL. I am still wondering how different RT3.10 is from RT3.2…

If you have to ask how bad an out-of-date RPM package is, you should
probably quickly look elsewhere. The whole advantage of RPM
installations is the ease of doing updates when someone else does
the work of rebuilding the package. If the package isn’t
being maintained, do yourself a favor and work from source.

However, this does bring up a different question that has been
answered before but I’m still confused by what I’ve seen about it.
RHEL is somewhat odd about backing in bugfixes from new program
versions without bumping the package version number. I think I
have seen claims that the RHEL3 perl 5.8.0 actually works correctly
with RT3. Can someone who is using it confirm that or explain what
problems to expect?

Les Mikesell
les@futuresource.com