Skip to content

Conversation

@karenetheridge
Copy link

Among other things, this also indicates that there are no dynamic prerequisites (META.json can be relied upon for the full list of dependencies). Therefore metacpan.org can also remove "and possibly others" from the list of dependencies.

Among other things, this also indicates that there are no dynamic
prerequisites (META.json can be relied upon for the full list of
dependencies). Therefore metacpan.org can also remove "and possibly others"
from the list of dependencies.
@charsbar
Copy link
Collaborator

There's no need to produce meta v2 yaml as META.json is already conformed to v2. cf. https://metacpan.org/release/ISHIGAKI/JSON-PP-4.16/source/META.json#L11-14

@charsbar charsbar closed this Dec 30, 2022
@karenetheridge
Copy link
Author

No, the important change here is that dynamic_config changes from 1 to 0.

@Grinnz
Copy link
Contributor

Grinnz commented Dec 30, 2022

which requires specification as meta-spec 2, and is downconverted when generating the yaml automatically.

@karenetheridge
Copy link
Author

I think this PR should be re-opened. Making these changes does improve the metadata.

@charsbar charsbar reopened this Mar 18, 2023
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.

3 participants