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

add [MetaJSON] to [@Basic] #554

Open
wants to merge 20 commits into
base: v7-in-progress
Choose a base branch
from

Conversation

karenetheridge
Copy link
Contributor

No description provided.

@karenetheridge karenetheridge force-pushed the topic/metajson_basic branch 3 times, most recently from 345eac6 to 43cd80b Compare May 18, 2016 21:06
@dolmen
Copy link
Contributor

dolmen commented May 19, 2016

It would be helpful to document this v6 change in the Pod of [@Basic].

@@ -45,6 +46,7 @@ It includes the following plugins with their default configuration:
* L<Dist::Zilla::Plugin::PruneCruft>
* L<Dist::Zilla::Plugin::ManifestSkip>
* L<Dist::Zilla::Plugin::MetaYAML>
* L<Dist::Zilla::Plugin::MetaJSON>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dolmen The plugin membership is listed here -- where else should it go?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was think about something more visible (well, as far as POD for a PluginBundle can be considered visible) such as a block in the DESCRIPTION section:

B<Note:> L<[MetaCPAN]|Dist::Zilla::Plugin::MetaJSON> is included since Dist::Zilla v6. 

@rjbs
Copy link
Owner

rjbs commented May 23, 2016

I'm not sure how I feel about special casing "can appear twice, whatever!" in a specific plugin, rather than just forcing people to update. I'm going to put this off for now.

@karenetheridge
Copy link
Contributor Author

karenetheridge commented May 23, 2016

The problem with having two MetaJSONs being a fatal error is that if then the distribution is built against Dist::Zilla 56, now they have no META.json file at all, which I think is a worse outcome for CPAN.

@rjbs rjbs added the v7 label Aug 6, 2016
@karenetheridge karenetheridge changed the base branch from dev-v6 to master July 3, 2017 00:02
@karenetheridge karenetheridge force-pushed the topic/metajson_basic branch 2 times, most recently from 4879151 to 2b77e25 Compare February 14, 2018 21:19
@karenetheridge karenetheridge force-pushed the topic/metajson_basic branch 3 times, most recently from d1605c2 to 9947478 Compare April 21, 2018 15:29
@rjbs rjbs assigned rjbs and karenetheridge and unassigned rjbs Apr 21, 2018
karenetheridge and others added 9 commits April 21, 2018 21:47
This will prevent discouraged formats from being used, even though CPAN::Meta
still lets some of them in (despite contradictory language in
CPAN::Meta::Spec).  Following the Lyon version roundtable, _ is no longer
interpreted as another dot in non-decimal versions, so the sort order can now
be different.
@karenetheridge karenetheridge changed the base branch from master to v7-in-progress December 16, 2018 02:49
@karenetheridge
Copy link
Contributor Author

updated to v7-in-progress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants