-
Notifications
You must be signed in to change notification settings - Fork 585
RMG: Simplify the corelist section #23401
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
Open
thibaultduponchelle
wants to merge
1
commit into
Perl:blead
Choose a base branch
from
thibaultduponchelle:rmg_improve_corelist_section
base: blead
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+13
−45
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -717,55 +717,23 @@ F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm> | |
|
||
=head4 Update C<Module::CoreList> with module version data for the new release | ||
|
||
Note that if this is a MAINT release, you should run the following actions | ||
from the maint branch, but commit the C<CoreList.pm> changes in | ||
I<blead> and subsequently cherry-pick any releases since the last | ||
maint release and then your recent commit. XXX need a better example | ||
|
||
[ Note that the procedure for handling Module::CoreList in maint branches | ||
is a bit complex, and the RMG currently don't describe a full and | ||
workable approach. The main issue is keeping Module::CoreList | ||
and its version number synchronised across all maint branches, blead and | ||
CPAN, while having to bump its version number for every RC release. | ||
See this brief p5p thread: | ||
|
||
Message-ID: <[email protected]> | ||
|
||
If you can devise a workable system, feel free to try it out, and to | ||
update the RMG accordingly! | ||
|
||
DAPM May 2013 ] | ||
|
||
F<corelist.pl> uses www.cpan.org to verify information about dual-lived | ||
modules on CPAN. It can use a full, local CPAN mirror and/or fall back | ||
on HTTP::Tiny to fetch package metadata remotely. | ||
|
||
(If you'd prefer to have a full CPAN mirror, see | ||
L<How to mirror CPAN|https://www.cpan.org/misc/how-to-mirror.html>) | ||
|
||
Change to your perl checkout, and if necessary, | ||
|
||
$ make | ||
|
||
Then, If you have a local CPAN mirror, run: | ||
|
||
$ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror | ||
|
||
Otherwise, run: | ||
In most cases, run: | ||
|
||
$ ./perl -Ilib Porting/corelist.pl cpan | ||
|
||
This will chug for a while, possibly reporting various warnings about | ||
badly-indexed CPAN modules unrelated to the modules actually in core. | ||
Assuming all goes well, it will update | ||
F<dist/Module-CoreList/lib/Module/CoreList.pm> and possibly | ||
F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm>. | ||
|
||
Check those files over carefully: | ||
|
||
$ git diff dist/Module-CoreList/lib/Module/CoreList.pm | ||
$ git diff dist/Module-CoreList/lib/Module/CoreList/Utils.pm | ||
|
||
If you have a L<local CPAN mirror|https://www.cpan.org/misc/how-to-mirror.html>, run: | ||
|
||
$ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror | ||
|
||
The procedure for MAINT releases is not straighforward and implies to pick past | ||
updates (e.g. from BLEAD-POINT) into the corelist. See | ||
L<Handling Module::CoreList in MAINT branches (Dave Mitchell)|https://www.nntp.perl.org/group/perl.perl5.porters/2013/03/msg200007.html>. | ||
|
||
=head4 Bump version in Module::CoreList F<Changes> | ||
|
||
Also edit Module::CoreList's new version number in its F<Changes> file. | ||
|
@@ -1567,13 +1535,13 @@ and F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm>. | |
|
||
=item * | ||
|
||
If you have a local CPAN mirror, run: | ||
In most cases, run: | ||
|
||
$ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror | ||
$ ./perl -Ilib Porting/corelist.pl cpan | ||
|
||
Otherwise, run: | ||
If you have a L<local CPAN mirror|https://www.cpan.org/misc/how-to-mirror.html>, run: | ||
|
||
$ ./perl -Ilib Porting/corelist.pl cpan | ||
$ ./perl -Ilib Porting/corelist.pl ~/my-cpan-mirror | ||
|
||
This will update F<dist/Module-CoreList/lib/Module/CoreList.pm> and | ||
F<dist/Module-CoreList/lib/Module/CoreList/Utils.pm> as it did before, | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Highlights from the linked message:
I‡ don't think a procedural checklist for doing a release is the correct time/place for philosophical debate, especially when the debate is about how difficult it is to follow the documented procedure(s)
__
‡. somebody with a github account who's never done a perl release