-
Notifications
You must be signed in to change notification settings - Fork 78
need to add a configure_requires entry for self at 7.05_01 if a version range is seen #215
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
Comments
This should happen before 7.06 is released. |
- issue a warning when version ranges are passed through to ExtUtils::MakeMaker, which cannot parse them and treats them as '0' (see Perl-Toolchain-Gang/ExtUtils-MakeMaker#215) - omit EXE_FILES argument to WriteMakefile() if there are no such files
- issue a warning when version ranges are passed through to ExtUtils::MakeMaker, which cannot parse them and treats them as '0' Perl-Toolchain-Gang/ExtUtils-MakeMaker#215 - added %P formatter code to [NextRelease] for the releaser's PAUSE id
bump 7.05x changes the handling of version ranges. It's important this carry over to the user side. |
- Add following line for make test to pass BUILD_DEPENDS+= p5-CPAN-Meta-Check-[0-9]*:../../devel/p5-CPAN-Meta-Check BUILD_DEPENDS+= p5-IPC-Run-[0-9]*:../../devel/p5-IPC-Run BUILD_DEPENDS+= p5-Log-Log4perl-[0-9]*:../../devel/p5-Log-Log4perl BUILD_DEPENDS+= p5-Test-FailWarnings-[0-9]*:../../devel/p5-Test-FailWarnings (upstream) - Update 5.036 to 5.039 --------------------- 5.039 2015-08-10 09:03:08-04:00 America/New_York - update required version of MooseX::Role::Parameterized; older versions work, but can cause a bunch of unwanted warnings 5.038 2015-08-07 22:16:50-04:00 America/New_York - [License] can be given a filename option to use instead of LICENSE - dzil listdeps --develop now exists as an alias for dzil listdeps --author (Karen Etheridge) - dzil authordeps now lists the Software::License class needed (thanks, David Zurborg) - PkgVersion now skips .pod files (thanks, David Golden) - build_element support added for [ModuleBuild] (thanks, David Wheeler!) - new native filefinder :ExtraTestFiles (thanks, Karen Etheridge) - [AutoPrereqs] now looks for develop prerequisites in xt/ (thanks, Karen Etheridge) - new file finder ':PerlExecFiles' (thanks, Karen Etheridge) - try harder to notice failure to set up build root, especially on Win32 (thanks, Christian Walde) - better errors when a global config package isn't available (thanks, Karen Etheridge) - added the "ignore" option to [Encoding] (thanks, Yanick Champoux) - allow ; authordep specifications to contain version ranges (thanks, Karen Etheridge) - better error when PAUSE credentials can't be loaded (thanks, David Golden) - fix documentation for the LicenseProvider role - improve errors when PPI failes to parse (thanks, Nick Tonkin) - sort list of executable files in Makefile.PL, for deterministic builds (thanks, Karen Etheridge) - omit configure-requires prerequisites from [MakeMaker]'s fallback prerequisites (used by older ExtUtils::MakeMaker) 5.037 2015-06-04 21:46:38-04:00 America/New_York - issue a warning when version ranges are passed through to ExtUtils::MakeMaker, which cannot parse them and treats them as '0' Perl-Toolchain-Gang/ExtUtils-MakeMaker#215 - added %P formatter code to [NextRelease] for the releaser's PAUSE id
@karenetheridge I agree this needs dealing with (cf #252). Would you agree that rather than |
I think so, yes. ..although others are making a legitimate case that we don't inject minimum versions when other features are seen (e.g. TEST_REQUIRES)... So I wonder if a simple warning would instead be sufficient? warn "hey, you're using this feature, which won't work right before 7.1101, but you're not specifying that minimum version. Are you sure? because that's not going to work very well."; |
After great reflection I think this is a wrong-headed idea. |
I used a range here: https://metacpan.org/source/ETHER/Dist-Zilla-Plugin-PromptIfStale-0.041/Makefile.PL#L24
In earlier EUMMs the version range is treated as 0, rather than respecting the stated prereq.
The text was updated successfully, but these errors were encountered: