KENTNL

• Website: blog.fox.geek.nz/

Recent Actions

• Commented on List your dist's prereqs where newer versions have become available
  I'm not sure I understand the response. My interpretation of what your module does in short is: Get the current deps of your packagefetch data from metacpan to work out newest versions of those depsset version requirements of your package...
• Commented on List your dist's prereqs where newer versions have become available
  Please don't do this, this is toxic to end users and dependencies alike, and makes it much harder for end users on older Perl's to use your code. This is much more likely to make a vendor yell at you...
• Commented on Test2/Test::Builder Update from the QAH
  > So far as I can see, in the absence of a viable third way, the options on the table were, basically I recall there was moves to propose a 3rd way, the "don't integrate yet, but have a way...
• Commented on Upping minimum version for Devel::Cover
  > I don't think you (or anyone else) should bother supporting 5.6.x That's not how this works. Its entirely fine that he doesn't want to support it himself. But expecting the 5.6'ers to turn up today and magically wave a...
• Commented on Upping minimum version for Devel::Cover
  Don't turn off travis testing. A Better option is to relocate 5.6 into the "allowed failures" section. That way the failures will still be obvious to anyone who cares, and wants to fix it. And that way when it gets...
• Commented on how to add switches to a perl program like plackup or dzil
  The other trick is simply: PERL5OPT="-d:Confess" dzil release Though that has the obvious downside that any child process spawned will inherit those switches. That, and I'm forever forgetting if its PERL5OPT or PERL5OPTS...
• Commented on Introducing IOD file format
  > In IOD you can also use this syntax: > > [section] > fruits = ["apple","orange","avocado"] But does this not simply re-expose the problem tinita was complaining about? It forces the consuming code to determine on a case-by-case basis whether...
• Commented on Introducing IOD file format
  That's incidentally one of the advantages of Config::MVP, which has an INI parser with similar rules to IOD. Usually, Each section in a Config::MVP based INI file has a corresponding Perl Package, and each Perl Package can define an 'mvp_multivalue_args'...
• Commented on Don't be afraid to rename your module / dist
  Also, Please remind me not to waste time with the edit process of commenting on blogs.perl.org to write a decent comment. blogs.perl.org, after allowing me to review my comment with preview multiple times, spontaneously decided to tell me my session...
• Commented on Don't be afraid to rename your module / dist
  Keep in mind that Role:: is a top level namespace. Maybe Role::Attr::CachedURL Though looking at what you have, a few things may be true: A) The role may not be applicable if you aren't using Moo and thus won't work...
• Commented on Let's top git.io
  I've modified my automated script also to commit with an email address that will cease to contribute to contribution stats. If I apply this to the whole repo retroactively it should take me down from 22k contributions to around 6k....
• Commented on Let's top git.io
  The limitations of Github search appear to be based on the technique by which they obtain the "most followed" people. That is, for any given query, there is a limit of 1000 results, even with pagination. https://github.com/paulmillr/top-github-users/blob/master/get-users.coffee#L13 After poking and...
• Commented on What is your release process?
  I have a few oddities, and I do things MyWay™, but I have a few tricks I don't see employed often which I find incredibly useful for a number of reasons. The most important to me, is the [Git::CommitBuild] plugin...
• Commented on The Four Major Problems with CPAN
  I think it would be "nice" to have something at least somewhat visible via the metacpan ui, but it definitely has to be "external" data to classes, data provided by user submission / crowd sourcing / data analysis , NOT...
• Commented on Pumpkin Perl - Redux
  I definitely prefer "pumpkin" and "pumpkin perl" over "perli". "perli" is just begging to increase the current rate at which people associate "perl" with "peril". Can't say I'm fond with that. After discussion with MST, it appears to me we're...
• Commented on Pumpkin Perl - Redux
  just wait, harry potter references are just around the corner. pumpkinbrew init pumpkinbrew abracadabra wand -v Image::Magick...
• Commented on Pumpkin Perl - Redux
  I have some thoughts, but they're not really "well, if we do x then we have to do y, z etc as well", more "there are many things y which are hard to get away with doing without doing x"....
• Commented on Bringing Perl5 to GitHub
  I feel the real let-down of github issues is its very weak on metadata vs RT. Metadata tools are limited to tagging and milestones, and thats basically it, and for seriously large projects this gets seriously out of hand. ie:...
• Commented on Visually graphing module dependencies
  Something else you may want to consider as a feature: Classifying dependencies by type, and augmenting the graph to suit, ie: Build/Configure/Runtime/Test/Develop dependencies And "Suggested/Recommended/Required" subsets of those dependencies. You could opt to include these in the depgraph, and colour/pattern...
• Posted Redesigning Package::Strictures to KENTNL
  _{Package::Strictures on metacpan} Design goals

  1. An infrastructure for having “optional” code blocks…
• Posted Musing on Perl::Critic config to KENTNL

  I've been exploring the Perl::Critic configuration file somewhat, and something struck me as unusual.

  It seems fine for using for the usecase of "inherit some predefined set of rules and apply them selectively", which works fine if you ju…

• Commented on Please Ensure ABSTRACT and LICENSE fields in your META.yml/json
  Yeah, actually, I was aware of this problem with the CPANdeps service months ago, possibly even years ago. Emitting only YAML is the default behaviour if you're using the basic (@Basic) bundle. Users can freely elect to not generate YAML,...
• Posted Please Ensure ABSTRACT and LICENSE fields in your META.yml/json to KENTNL

  I've been opening quite a few bugs lately for distributions failing these 2 criteria, so, I figured I'd save everyone some effort and unify it cohesively.

  Reason

  While it may seem a trivial squabble, ABSTRACT and LICENSE…

• Commented on Looking up the location of an IP address
  "Web site localisation: automatically redirecting the user to the best default site, perhaps changing the language in the process." I should point out if it wasn't already obvious that you should never infer language by source IP's country code. Its...

Comment Threads

• Aristotle commented on Test2/Test::Builder Update from the QAH

  For TCM to work with Test2, every single module you use to output tests must also use Test2.

  This, however, I will call unqualified nonsense. Let me demonstrate to you why:

  1. Test::More will not be changing at all. Yet it will be able to coöperate with Test2-based modules just fine, by using a Test::Builder whose guts have been swapped for a Test2 wrapper.
  2. If it were true, that would mean that Test2 could not be released as part of Test::Builder without a simultaneous re-release every single test module on CPAN, ported to Test2. Otherwise CPAN …
• blog.urth.org commented on Test2/Test::Builder Update from the QAH

  Aristotle said:

  Thus the claim that Test modules would have to be written specifically against Test2, in order to be able to work with other Test2-based modules, is simply factually incorrect.

  That wasn't what I was trying to claim. Maybe I don't understand what you and Leon wanted to happen.

  My point was simply that Test2-using tools will not cooperate with code that uses the existing pre-Test2 Test::Builder. Of course, if Test::Builder is using Test2 under the hood, then tools using Test::Builder do not also have to change (but AFAICT no one is say…

• Aristotle commented on Test2/Test::Builder Update from the QAH

  Maybe I don't understand what you and Leon wanted to happen.

  Yes, sorry, I’ll be publishing a long-form, detailed version of the proposal very soon. I’ve realised the proposal is (either largely or entirely) non-understood – the abridged version I presented on the fly at that table was insufficient. (I had hoped but failed to have it out there sufficiently early before the QAH that people could digest it in detail.)

  My point was simply that Test2-using tools will not cooperate with code that uses the existing pre-Test2 Test::Builder.

• Chad 'Exodist' Granum commented on Test2/Test::Builder Update from the QAH

  One of the initial options discussed as early as last year was this:

  Test2 and Test::Builder remain separate. Tools pick one a build with it. To use both together you load a shim such as Test2::Legacy, which replaces Test::Builder with the alternative guts.

  This was the alternative being discussed in the Test2 meeting on day 1 of the 2016 hackathon. We decided it was not the right plan. My main reason for opposing this plan is that nothing stops people from updating old modules to use Test2, and also auto-loading the shim to insure they do not break things that depend on them…

• Steve Bertrand commented on List your dist's prereqs where newer versions have become available

  Hi Kent,

  Thanks for the feedback. The software by default lists only one's own dependencies. Out of ~30 of my CPAN distributions, I believe only two of them aren't 5.8 compliant (due to external dependencies).

  Also, I have automation software that allows me to test all reverse dependencies after any change to one of my distributions, so:

  cd ~/repos/mock-sub
  git pull
  # make changes, perhaps bumping one of my
  # own prereq versions
  
  My [Test::BrewBuild](https://metacpan.org/release/Test-BrewBuild) software does a lot of t…