On Wed, Oct 31, 2012 at 10:06 AM, Tim Cutts t...@sanger.ac.uk wrote:
On 31 Oct 2012, at 16:45, Ram ram0...@gmail.com wrote:
On my Mac, where I do some RT tinkering as a standalone build, I have an
rt-support directory in my home directory, and I put all the libraries RT
needs in there, and
Date: Wed, 31 Oct 2012 10:25:31 -0700
From: Thomas Sibley t...@bestpractical.com
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Perl conflicts
Message-ID: 50915f0b.3050...@bestpractical.com
Content-Type: text/plain; charset=UTF-8
On 10/31/2012 09:45 AM, Ram wrote:
Any other
On 11/01/2012 12:50 PM, Ram wrote:
There are tools to do it (cpan2rpm comes to mind) and of course
something like perlbrew (oft mentioned in this type of discussion)
which I believe that compiles things into 'executables'.
perlbrew doesn't compile Perl modules into executables. perlbrew
Date: Wed, 31 Oct 2012 12:47:49 -0500
From: k...@rice.edu k...@rice.edu
To: Thomas Sibley t...@bestpractical.com
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Perl conflicts
Message-ID: 20121031174749.gv2...@aart.rice.edu
Content-Type: text/plain; charset=us-ascii
On Wed
On 30 Oct 2012, at 19:47, Thomas Sibley t...@bestpractical.com wrote:
On 10/30/2012 12:21 PM, Ram wrote:
How do folks deal with perl conflicts? We normally use RPMs for
everything but that's not practical given the relatively high-version
requirements of the rt4 branch so CPAN seems the only
Date: Wed, 31 Oct 2012 10:10:56 +
From: Tim Cutts t...@sanger.ac.uk
To: Thomas Sibley t...@bestpractical.com
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Perl conflicts
Message-ID: b823eddb-03a1-4bd4-bc4f-e5c6de19c...@sanger.ac.uk
Content-Type: text/plain; charset=us
On 31 Oct 2012, at 16:45, Ram ram0...@gmail.com wrote:
On my Mac, where I do some RT tinkering as a standalone build, I have an
rt-support directory in my home directory, and I put all the libraries RT
needs in there, and I point my PERL5LIB and DYLD_LIBRARY_PATH variables at
it whenever
On 10/31/2012 09:45 AM, Ram wrote:
Any other ideas?
It's worlds-apart easier and less error prone to use an entirely
separate perl build instead of just a separate perl lib path. See perlbrew.
We're hiring! http://bestpractical.com/jobs
On Wed, Oct 31, 2012 at 10:25:31AM -0700, Thomas Sibley wrote:
On 10/31/2012 09:45 AM, Ram wrote:
Any other ideas?
It's worlds-apart easier and less error prone to use an entirely
separate perl build instead of just a separate perl lib path. See perlbrew.
+1 It is much, much easier and
On 10/30/2012 12:21 PM, Ram wrote:
How do folks deal with perl conflicts? We normally use RPMs for
everything but that's not practical given the relatively high-version
requirements of the rt4 branch so CPAN seems the only practical
approach.
Use a completely separate build of perl just for
10 matches
Mail list logo
