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
update Makefile.PL to meta-spec v2 and set dynamic_config to 0 #835
Conversation
What do we gain by applying this patch? |
repository => { | ||
type => 'git', | ||
url => 'https://github.com/kraih/mojo.git', | ||
web => 'https://github.com/kraih/mojo', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why three settings? MetaCPAN seems to already have all the information it needs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With only the one URL, MetaCPAN simply says "clone repository" instead of having separate "Repository" and "Clone" links. In this case I am just following the meta-spec v2.
Does it have static prereqs? I thought it loaded a couple of modules for older perls. Mojolicious wasn't working correctly when I installed it on one perl and then upgraded perl but not Mojolicious. So I think the dynamic aspect is certainly there. |
Looks like MetaCPAN uses the |
@zoffixznet upgrading perl in-place while having modules installed from CPAN that aren't upgraded will always result in breakage. Mojolicious has no dynamic dependencies. |
@kraih The message "and possibly others" is referring to dynamic dependencies, not optional dependencies. For CPAN tools to be aware of the optional dependencies of Mojolicious they would need to be added as "recommends" or "suggests"; however optional dependencies are not relevant to the |
From my understanding it would be On Tue, Aug 25, 2015 at 8:39 AM Dan Book notifications@github.com wrote:
|
update Makefile.PL to meta-spec v2 and set dynamic_config to 0
dynamic_config
should really be disabled so that CPAN tools know that Mojolicious has static prerequisities (as per https://metacpan.org/pod/CPAN::Meta::Spec#dynamic_config). To do this, theMETA_MERGE
contents are updated to follow v2 of the META spec. The diff of the resulting META.json with the current META.json is linked below.https://gist.github.com/Grinnz/ca3f85988463e34b8118