<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content=text/html;charset=UTF-8>
<META content="MSHTML 6.00.2900.5764" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><B>From:</B> <A title=swatt@infobal.com
href="mailto:swatt@infobal.com">Stuart Watt</A> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>Why would you do that? If the module you're installing fails its tests,
you should file a bug report. What kind of error? IME you shouldn't ever want
to or need to force install a module. This should be a *colossal* red flag to
you. <BR><BR>...<BR><BR>/joel <BR></DIV>It is very possible that the tests
fail because the tests are wrong, not the module. I use a Perl that does not
have fork emulation on Windows, partly for performance. Many tests assume
fork, even where the modules they are testing do not depend on it. Yes, these
modules should be reported, but you don't need to wait for a new release, nor
is the module necessarily compromised. Authors cannot always test on a wide
range of platforms. I find a good few modules fail tests for system/platform
reasons rather than because of bugs in the code. <BR><BR>Modules I know fail
on Windows without fork but generally don't care include: DBD::mysql,
Test::NoWarnings, WWW::Mechanize, HTTP::Server::Simple, Cache::Cache, and
DBD::SQLite. Most of these have tests that assume fork. Some get caught by
file system differences and permissions differences. <BR><BR>You might have a
wider concern if you are using a "standard" build (if such a thing exists) but
it is at least sometimes justifiable to look through the tests that fail and
make a judgment call. <BR><BR>--S<BR>
<DIV class=moz-signature>-- <BR><SPAN style="COLOR: rgb(102,0,0)">Stuart
Watt<BR>ARM Product Developer<BR>Information Balance</SPAN></DIV>
<P><FONT face=Arial size=2></FONT>
<P><FONT face=Arial size=2>Hi,</FONT>
<P><FONT face=Arial size=2></FONT>
<P><FONT face=Arial size=2>Sometimes I see that I can't install some perl
modules, but then I found a ppm package that can be installed, and that
module has the same version as the ones I couldn't install using the cpan
shell.</FONT>
<P><FONT face=Arial size=2></FONT>
<P><FONT face=Arial size=2>So probably the tests are done wrong.</FONT>
<P><FONT face=Arial size=2></FONT>
<P><FONT face=Arial size=2>Some tests (like the one for DBD::SQLite) also
crash the perl interpreter, not only that the tests don't succeed.</FONT>
<P><FONT face=Arial size=2></FONT>
<P><FONT face=Arial size=2>And as you said, most of the tests use fork and
then I know why they are not working under Windows.</FONT>
<P><FONT face=Arial size=2></FONT>
<P><FONT face=Arial size=2>If we need to deploy a Catalyst app under Linux, is
not so hard to install modules from CPAN using the cpan shell, but it might be
very hard to install some modules under Windows, so it would be very good if
we could use local::lib to pre-install the necessary modules.</FONT>
<P><FONT face=Arial size=2></FONT>
<P><FONT face=Arial size=2>And regarding my question, in local::lib's POD, I
read that:</FONT>
<P><FONT face=Arial size=2></FONT>
<P><FONT face=Arial size=2> From the shell -</FONT>
<P><FONT face=Arial size=2> perl -MCPAN
-Mlocal::lib=my_lwp -e 'CPAN::install(LWP)'</FONT>
<P><FONT face=Arial size=2></FONT>
<P><FONT face=Arial size=2>Where in this command line can I add the "force"
parameter, or is there another way of installing perl modules in the local
directory?</FONT>
<P><FONT face=Arial size=2></FONT>
<P><FONT face=Arial size=2>And, another question:</FONT>
<P><FONT face=Arial size=2>Can we deploy an app that uses local::lib without
having shell access but only ftp access if local::lib is not installed?</FONT>
<P><FONT face=Arial size=2>(It would be interesting to know, although I never
needed it until now.)</FONT>
<P><FONT face=Arial size=2></FONT>
<P><FONT face=Arial size=2>Thanks.</FONT>
<P><FONT face=Arial size=2></FONT>
<P><FONT face=Arial size=2>Octavian</FONT>
<P>
<P><FONT face=Arial size=2></FONT> </P></BLOCKQUOTE></BODY></HTML>