-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BLOCKER: Dist::Zilla::Plugin::MakeMaker gets Perl minimum version wrong #148
Comments
On Mon, Feb 25, 2013 at 12:29:48AM -0800, Ovid wrote:
Are you sure that's what you specified? I only get a "Perl" key in -doy |
Ack, sorry about that. I has "Perl", not "perl". The above was a typo. As far as I can tell, Cheers, |
the Is that the correct approach or simply adding perl to |
I think I'm OK with N/A reports. I'd rather not have the code even tested on unsupported systems, but N/A is better than a failure. OvidTwitter - http://twitter.com/OvidPerl/
|
I'm not sure what the proposed change would do, in practice. That is: in what way is it better than "use 5.10.0;" and why? |
I am OK also with N/A reports. Thanks 👍 |
Where's this at? Is there still a blocker? Is there anything to be done at all? |
I am closing this ticket due to lack of response. I think it's okay to be closed anyway. :) |
Loving Dist::Zilla so far, but I've hit a critical blocker. I'm sure it's me just not reading the right docs, but is there any workaround I can use to get my generated
Makefile.PL
to assert the correct minimum version of Perl?In my
dist.ini
, I have the following:That wrote the following in my
Makefile.PL
:That led to the following bug report: https://rt.cpan.org/Public/Bug/Display.html?id=83563
In short,
perldoc ExtUtils::MakeMaker
says this is how you assert the minimum Perl version:So far all workarounds I've tried have failed, including using MinimumPerl, which swears that I need Perl 5.12.0, even though
perlver --blame
on all files reveals 5.10.0 to be the highest version needed.I would like to avoid
AutoPrereqs
yet because it's missed some prereqs at work (I cannot replicate the use case).Cheers,
Ovid
The text was updated successfully, but these errors were encountered: