add Sub::Name, perl 5.010 to test recommendations

[karenetheridge]

no other metadata or prereqs have changed (verified with 'dzil build --not' and a recursive diff against the last uploaded release)

[doy]

Any reason you removed this use statement?

[karenetheridge]

On Fri, Apr 25, 2014 at 06:03:02PM -0700, Jesse Luehrs wrote:

@@ -1,9 +1,7 @@
-package Try::Tiny;
-use 5.006;

Any reason you removed this use statement?

If it remains, [AutoPrereqs] will pick up on it, which will result in an extra { runtime => { recommends => { perl => '5.006' } } } that doesn't add any value.

[doy]

Why would it do that? It's already in the dist.ini as a hard dep, so I don't see why it should make a difference either way. If [Prereqs::Soften] can't handle having a 'requires' dep on one version of something and a 'recommends' dep on a higher version of that same thing, I think that it should be fixed, rather than removing potentially useful metadata.

[karenetheridge]

On Fri, Apr 25, 2014 at 09:00:09PM -0700, Jesse Luehrs wrote:

@@ -1,9 +1,7 @@
-package Try::Tiny;
-use 5.006;

Why would it do that? It's already in the dist.ini as a hard dep, so I don't see why it should make a difference either way. If [Prereqs::Soften] can't handle having a 'requires' dep on one version of something and a 'recommends' dep on a higher version of that same thing, I think that it should be fixed, rather than removing potentially useful metadata.

It's not "it can't handle it" - but that it would be doing exactly what
it's told to do - change all 'perl' requires that it sees to 'recommends'.
When it runs, all there is is the 'test' entry, which is the one we want to
soften (5.010).

The plugin ordering matters - the 5.006 prereq is not added as a 'requires'
prereq until after [Prereqs::Soften] runs.

Try doing a build, move the build dir aside, do another build, and then a
diff -r to see the difference.