Skip to content
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

Merged
merged 2 commits into from Aug 28, 2015

Conversation

Grinnz
Copy link
Contributor

@Grinnz Grinnz commented Aug 25, 2015

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, the META_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

@kraih
Copy link
Member

kraih commented Aug 25, 2015

What do we gain by applying this patch?

repository => {
type => 'git',
url => 'https://github.com/kraih/mojo.git',
web => 'https://github.com/kraih/mojo',
Copy link
Member

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.

Copy link
Contributor Author

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.

@zoffixznet
Copy link
Contributor

dynamic_config should really be disabled so that CPAN tools know that Mojolicious has static prerequisities

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.

@kraih
Copy link
Member

kraih commented Aug 25, 2015

Looks like MetaCPAN uses the dynamic_config field to decide if it should display the message and possibly others in the dependency list. Considering our extra runtime dependencies for certain features, isn't that exactly what we want?

@Grinnz
Copy link
Contributor Author

Grinnz commented Aug 25, 2015

@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.

@Grinnz
Copy link
Contributor Author

Grinnz commented Aug 25, 2015

@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 dynamic_config metadata.

@jberger
Copy link
Member

jberger commented Aug 25, 2015

From my understanding it would be suggests since they shouldn't be
attempted for installation.

On Tue, Aug 25, 2015 at 8:39 AM Dan Book notifications@github.com wrote:

@kraih https://github.com/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 dynamic_config metadata.


Reply to this email directly or view it on GitHub
#835 (comment).

kraih added a commit that referenced this pull request Aug 28, 2015
update Makefile.PL to meta-spec v2 and set dynamic_config to 0
@kraih kraih merged commit 20a8efa into master Aug 28, 2015
@Grinnz Grinnz deleted the meta-spec-2 branch September 6, 2015 21:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants