From: Stuart Watt
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.
...
/joel
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.
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.
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.
--S
--
Stuart Watt
ARM Product Developer
Information Balance
Hi,
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.
So probably the tests are done wrong.
Some tests (like the one for DBD::SQLite) also crash the perl interpreter,
not only that the tests don't succeed.
And as you said, most of the tests use fork and then I know why they are not
working under Windows.
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.
And regarding my question, in local::lib's POD, I read that:
From the shell -
perl -MCPAN -Mlocal::lib=my_lwp -e 'CPAN::install(LWP)'
Where in this command line can I add the "force" parameter, or is there
another way of installing perl modules in the local directory?
And, another question:
Can we deploy an app that uses local::lib without having shell access but
only ftp access if local::lib is not installed?
(It would be interesting to know, although I never needed it until now.)
Thanks.
Octavian
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
