[rt-users] DEV dependencies

[Matthew Watson]

It /Seems/ to be just used for the testing, atleast in 3.2

rt3-1 local/rt# grep -r Mechanize *
lib/t/03web.pl:use WWW::Mechanize;
lib/t/03web.pl:my $agent = WWW::Mechanize->new();
lib/t/03web.pl.in:use WWW::Mechanize;
lib/t/03web.pl.in:my $agent = WWW::Mechanize->new();
rt3-1 local/rt#

Matt.

> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-
> bounces at lists.bestpractical.com] On Behalf Of beer
> Sent: Thursday, March 31, 2005 5:06 AM
> To: rt-users at lists.bestpractical.com
> Subject: [rt-users] DEV dependencies
> 
> Hello All
> 
> I searched the archives and didnt find my answer so I hope I am not
> repeating anything.
> 
> My question is:  How dependant is RT on the DEV dependencies listed in
the
> output of the testdeps target?
> 
> In the environment where I'll be running RT, we are using a
semi-homegrown
> host configuration system.  I cannot install anything using cpan.
This
> has not been a problem for most things.  cpan2rpm or cpanflute2 have
been
> very useful for creating and cataloging rpms into our system.
However,
> WWW-Mechanize has some dependencies that I am having trouble getting
> around.
> 
> I have a working configuration area and was able to use it to install
an
> RT instance on my local machine but I had to 'unrequire' the Mechanize
> module.  Everything seems to be working fine, but since this is merely
a
> poc installation and it isnt really get hit with requests, I wanted to
get
> an idea of what I am likely screwing up by not installing Mechanize.
> 
> Thanks
> 
> -bill
> 
> _______________________________________________
> 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

This email and any files transmitted with it are confidential and intended solely for the 
use of the individual or entity to whom they are addressed. Please notify the sender 
immediately by email if you have received this email by mistake and delete this email 
from your system. Please note that any views or opinions presented in this email are solely
 those of the author and do not necessarily represent those of the organisation. 
Finally, the recipient should check this email and any attachments for the presence of 
viruses. The organisation accepts no liability for any damage caused by any virus 
transmitted by this email.