Steffen from modules@perl.org responded to my email yesterday and made me a co-maintainer of String::Strip. I've applied the 64 bit bug fix to it, and pushed 1.02 to CPAN. Thanks for everyone who responded to my thread yesterday about requesting co-maintainer. This is how open source is supposed to work!
String::Strip has a problem on 64 bit environments, and a release has not been made in over 10 years. I have sent an email to modules@perl.org asking for COMAINT as the author has apparently not been responding to RT tickets.
https://rt.cpan.org/Public/Bug/Display.html?id=70028
http://search.cpan.org/dist/String-Strip
If anyone sees this post and has the magic powers to make this happen, I'd be very appreciative if they could help out.
I'm looking for a logger module like Log::Log4Perl but one I can hand a filename to and be done with it. No /etc configuration files or other crap to deal with, and still have debug/warn/etc log levels.
Any ideas? Something like:
use Log::EasyLog;
my $logger = Log::EasyLog->new( file => '/tmp/mylogfile' );
I've started using 'cpanm -n Module' to install Perl modules. The '-n' tells cpanminus to skip testing and just install the module.
"What, are you insane?"
Nope, I have just found that for most Perl modules, it is more time efficient to skip testing on the initial install, and sort out any problems later. Especially with a setup you know that works.
If I was installing a new application for the first time, I would probably not skip the tests however.
Next time I upgrade DBIx::Class it will probably tell me I need to get a haircut.
DBIx::Class::Schema::connection(): You provided explicit AutoCommit => 0 in your connection_info. This is almost universally a bad idea (see the footnotes of DBIx::Class::Storage::DBI for more info). If you still want to do this you can set $ENV{DBIC_UNSAFE_AUTOCOMMIT_OK} to disable this warning. at lib/Territory/Model/TerritoryDB.pm line 23