...@cedrat.com - http://www.cedrat.com
-Message d'origine-
De : rt-users-boun...@lists.bestpractical.com
[mailto:rt-users-boun...@lists.bestpractical.com] De la part
de Wes Modes
Envoyé : 4 novembre 2010 22:02
À : RT Users
Objet : [rt-users] Why I am recommending 3.6 over 3.8 to my boss
On Nov 5, 2010, at 5:26 AM, Robert Grasso wrote:
This is my own opinion : as you increase your Unix/Linux/RedHat skills, you
will feel less concerned by such issues.
As you increase the number of systems you need to manage, you will feel more
concerned by such issues.
A good package
On Thu, 4 Nov 2010, Wes Modes wrote:
I CAN do a manual install of RT3.8 using the Best Practical install
scripts. It is not terribly hard. However, the long-term costs of this
Hi Wes. One of the biggest problems here is often over-looked. When you
build the app yourself you are taking
I CAN do a manual install of RT3.8 using the Best Practical install
scripts. It is not terribly hard. However, the long-term costs of
this are large. The install scripts put all the binaries,
configuration files, and libraries in the wrong places for RHEL/CentOS,
and working outside the
On Nov 5, 2010, at 8:59 AM, Josh Narins wrote:
They are never clobbered with:
./configure --prefix=/opt/local
so now you need your own private copy of perl in /opt/local as well else
the package system may clobber your perl modules installed by hand too. It
becomes a very tangled web
On Fri, Nov 05, 2010 at 09:04:07AM -0400, Vick Khera wrote:
On Nov 5, 2010, at 8:59 AM, Josh Narins wrote:
They are never clobbered with:
./configure --prefix=/opt/local
so now you need your own private copy of perl in /opt/local as well else
the package system may clobber your
Wes,
I strongly recommend going with the 3.6 version of RT. The install takes a
few minutes, and it otherwise meets all the requirements of our project.
Migration of old queues is simple. There is cost savings in the near and
long-term.
RT 3.6 is no longer being actively developed
--- On Fri, 11/5/10, Jesse Vincent je...@bestpractical.com wrote:
From: Jesse Vincent je...@bestpractical.com
Subject: Re: [rt-users] Why I am recommending 3.6 over 3.8 to my boss
To: Wes Modes wmo...@ucsc.edu
Cc: RT Users rt-users@lists.bestpractical.com
Date: Friday, November 5, 2010, 10:22 AM
On Fri, Nov 05, 2010 at 10:32:22AM -0700, Joseph Spenner wrote:
--- On Fri, 11/5/10, Jesse Vincent je...@bestpractical.com wrote:
./confiure --enable-layout=RH
This is interesting, since I use CentOS (RedHat) and had absolutely no issue
installing RT 3.8.8. What does the above option
I bet Best Practical would produce RPMs for you if you paid them to.
On Thu, Nov 4, 2010 at 5:01 PM, Wes Modes wmo...@ucsc.edu wrote:
Dear Boss:
I strongly recommend going with the 3.6 version of RT. The install takes a
few minutes, and it otherwise meets all the requirements of our
If you search for rt 3.8 spec file you will find some spec files that
do work for fedora and other variants. It wasn't too difficult to take
one of those and morph it for our custom use.
Biggest issue I had was taking the time to package up perl dependencies
as rpms to store in our repo long
Agreed. One sysadmin managing a score of mission-critical servers and a
half dozen projects does not allow much time for one-offs and special
cases. Over my 25 years of sysadmin experience, I've learned that the
most efficient thing I can do as a sysadmin is to allow the package
management
Get yourself a copy of cpan2rpm. It simplifies creating the specs from the
ground up greatly.
On 5/11/10 12:49 PM, Dallas Wisehaupt dal...@craigslist.org wrote:
If you search for rt 3.8 spec file you will find some spec files that
do work for fedora and other variants. It wasn't too difficult
Dear Boss:
I strongly recommend going with the 3.6 version of RT. The install takes a few
minutes, and it otherwise meets all the requirements of our project. Migration
of old queues is simple. There is cost savings in the near and long-term.
There is no rpm of RT3.8 that works for RHEL
Migration from 3.6 to 3.8 is a non-issue. It is easy, and not even worth
considering as a problem. It isn't any more difficult to move from 3.6
to 3.8 as it is to move from 3.6.x to 3.6.y.
We were stuck on the RPM issue for a while, but I stopped caring. I
don't trust the RPMs produced for
15 matches
Mail list logo
