• About: I provide solutions.
  • Commented on Test::More has lots of crazy new development that's breaking my modules
    If the tester is not testing Test::More, why is it using a trial version of Test::More? Shouldn't the cpantester node be using the production version of everything that is not actively under test? Just my $0.02....
  • Commented on /usr/local/bin rant
    /usr/local, on some platforms, is not secure. On other platforms, /usr/contrib is an unsecure location. There is a reason not to include it in root's default path. Under cron (or system startup, or manually running scripted tasks), I typically have...
Subscribe to feed Recent Actions from MidLifeXis

  • code_monkey commented on /usr/local/bin rant

    Here's a nice thread that speaks to the cpan v package manager choice.

    I think developers prefer CPAN because they can immediately get things done, sys admins like order and integration of components into their environment that will play nice with their tool chains. Ultimately if you are deploying across multiple platforms flexibility is key, however in a homogenous environment rapid deployment using native tools is preferred. If the ai…

  • Alex Kapranoff commented on /usr/local/bin rant

    Looks like your questhub/play-perl links are broken here.

  • Vyacheslav Matyukhin commented on /usr/local/bin rant

    Oops, I copy-pasted Neil's code and forgot to replace the link. Thanks! :)

  • Robert Rothenberg commented on Test::More has lots of crazy new development that's breaking my modules

    As a module author, I also don't want to see fails for spurious reasons for my modules.

    I think the only time I've used that as a reason to not use a module was when that module hadn't been updated in several years, and consistently fails on recent versions of Perl.

    I believe that CPAN Testers has a way that you can mark specific tests as not-applying just for…

  • Ether commented on Test::More has lots of crazy new development that's breaking my modules

    > I don't think CPAN Testers is doing the right thing by using broken Test::More's that aren't available for normal installations.

    I strongly disagree. What if these Test::More changes *were* production ready? Receiving these failing reports, before Test::More sees a stable release, would be vital to identifying issues with your code, so you have a chance to fix it before that stable release and everyone is affected. The smokers can't know whether this trial is nearing production readiness or not.

    CPAN test reports are my best indicator of whether my code is working for eve…

Subscribe to feed Responses to Comments from MidLifeXis

About is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is run by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.