-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 17 Jul 2007 at 07:09 (-0400), Kevin Falcone wrote:
Makefile.PL for RTFM normally prompts you to find RT.pm, which is how it
would know to look in your local/lib
Kevin,
Yes, it did. It turns out I gave it the path to the default RT.pm, no
On Jul 16, 2007, at 11:46 PM, Mike Friedman wrote:
One more thing. I didn't actually run 'perl Makefile.PL'.
Instead, because of my 'virtual private server' environment, I had
to run this:
perl Makefile.PL `cat ../perl5prefs-ist-rt `
where the file '../perl5prefs-ist-rt' contains setti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 16 Jul 2007 at 13:49 (-0400), Jesse Vincent wrote:
It turns out that the Makefile generated by Makefile.PL didn't include
my ../local/lib in the 'initdb' target definition. So, I edited the
Makefile manually (which I know you're not suppos
On Jul 13, 2007, at 5:22 PM, Mike Friedman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 12 Jul 2007 at 14:15 (-0700), Mike Friedman wrote:
It turns out that the Makefile generated by Makefile.PL didn't
include my ../local/lib in the 'initdb' target definition. So, I
edite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 12 Jul 2007 at 14:15 (-0700), Mike Friedman wrote:
It turns out that the Makefile generated by Makefile.PL didn't include my
../local/lib in the 'initdb' target definition. So, I edited the Makefile
manually (which I know you're not suppos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm trying to install RTFM 2.2.0RC5 on a 'virtual private server', where
everything must go inside my home directory and I'm a non-privileged user.
I've already had RT 3.6.3 installed and running fine, so I just followed
the install instructions in
