[rt-users] Installing RT on RHEL 4.

[Scott T. Hildreth]

Okay, 1.99 was the beta of Modperl2, the latest is 2.0 Rc4.  You might
want to upgrade.

On Wed, 2005-03-09 at 16:09 -0500, Paul Crossman wrote:
> Hmmm, ok, maybe redhat put the perlmod2 beta on RHEL.  I'd be surprised if
> they did, but ther version of perlmod installed on server here is 
> mod_perl-1.99_16-4.  I used modperl1 strictly based on the version number of
> the RPM.  Am I mistaken?
> 
> Paul C.
> 
> 
> -----Original Message-----
> From: Scott T. Hildreth [mailto:shildret at scotth.emsphone.com] 
> Sent: Wednesday, March 09, 2005 12:37 PM
> To: Paul Crossman
> Cc: Rt-Users
> Subject: Re: [rt-users] Installing RT on RHEL 4.
> 
> I don't use RHEL, but you indicated perlmod1, maybe a typo.  ModPerl2 is
> for use with Apache2.
> 
> On Wed, 2005-03-09 at 11:49 -0500, Paul Crossman wrote:
> > Hello, I'm installing RT on RHEL 4 and I'm wondering if anyone has
> > done this yet?
> > 
> >  
> > 
> > I'm installing with MySQL, Apache 2, and perlmod1.  
> > 
> >  
> > 
> > I'm using RHEL4 since it comes with more stuff RT needs out of the
> > box, however, I’m having issues with 4 specific perl modules:
> > 
> >  
> > 
> >         Apache::Request
> > 
> >         Apache::DBI 
> > 
> >         Log::Dispatch
> > 
> >         MIME::Entity 
> > 
> >  
> > 
> > CPAN won't install them, mostly because they won’t pass the test
> > conditions.  Has anyone else tried using RHEL for their RT install?
> > Does anyone have any possible starting points?  I have tried building
> > the mods from source, and the sources all have the failing test
> > issues.
> > 
> >  
> > 
> > Thanks,
> > 
> > Paul C.
> > 
> > 
> > _______________________________________________
> > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> > 
> > RT Administrator and Developer training is coming to your town soon!
> (Boston, San Francisco, Austin, Sydney) Contact training at bestpractical.com
> for details.
> > 
> > Be sure to check out the RT Wiki at http://wiki.bestpractical.com
-- 
Scott T. Hildreth <shildreth at allantgroup.com>