CPAN makes me cranky, but trying to package all the perl modules as RPMs
makes me crankier. It's like wrapping one packaging system around
another one, and fighting with both of them.
The reality is, every time RHEL updates perl, RT will break. I solve
this by having an identical test system. I apply the updates, see what
breaks, and then reinstall the perl modules in question using CPAN.
Once I figure this out, I do the same process on the production RT
system during a maintenance window. It actually works out pretty well
now that I am used to this, but it is less than ideal.
RHEL is a major platform, and I'd love it if BestPractical supported it
in some official way so we don't have these kinds of problems we have to
work around.
Still, I love RT and praise it to anyone who will listen.
On 12/13/10 11:04 AM, Khusro Jaleel wrote:
I'm stuck between a rock and a hard place, then. The Redhat people are
telling me to *avoid* CPAN like the plague, and most people [1] seem to
have accomplished the install on CentOS systems using a combination of
packages + CPAN, which is something else that is NOT recommended to do.
I wish Best Practical did come up with their own packages, especially
for Redhat, it would make things so much easier.
[1] - http://requesttracker.wikia.com/wiki/CentOS5InstallPlusSome
