Skip to content

Add directory-diff.pl script#24046

Open
Corion wants to merge 1 commit intoPerl:bleadfrom
Corion:rmg-directory-diff
Open

Add directory-diff.pl script#24046
Corion wants to merge 1 commit intoPerl:bleadfrom
Corion:rmg-directory-diff

Conversation

@Corion
Copy link

@Corion Corion commented Dec 28, 2025

This is to make the step of comparing two installed versions of Perl a bit easier and less dependent on (POSIX) shell tools, at the price of installing Algorithm::Diff.

Usage:

perl Porting/directory-diff.pl -l 's/5.43.6/5.43.7/g' /tmp/perl-5.43.6 /tmp/perl-5.43.7

The patch also adds a paragraph to the Release Managers Guide on installing the additional module(s), currently only Algorithm::Diff .


  • This set of changes does not require a perldelta entry.

@Corion Corion force-pushed the rmg-directory-diff branch from 691ca37 to a904bf0 Compare December 28, 2025 19:37
@jkeenan
Copy link
Contributor

jkeenan commented Jan 15, 2026

@Corion, this pull request has a number of porting test failures which should be fixed before we undertake a full discussion. Can you fix?

@jkeenan jkeenan added the Infrastructure Things needed to maintain Perl development label Jan 15, 2026
@Corion Corion force-pushed the rmg-directory-diff branch from 730a64a to 5a68022 Compare January 15, 2026 20:39
This is to make the step of comparing two installed versions of Perl
a bit easier and less dependent on (POSIX) shell tools, at the price
of installing Algorithm::Diff.

Usage:

  perl Porting/directory-diff.pl -l 's/5.43.6/5.43.7/g' /tmp/perl-5.43.6 /tmp/perl-5.43.7
@Corion Corion force-pushed the rmg-directory-diff branch from 5a68022 to 1fe042c Compare January 15, 2026 20:40
@Corion
Copy link
Author

Corion commented Jan 15, 2026

Whoops! The above force-pushes address the failing tests (that I did not run, I admit)

For example, suppose the about-to-be-released version is 5.10.1 and the
previous is 5.10.0:
For example, suppose the about-to-be-released version is 5.43.6 and the
previous is 5.43.7:
Copy link
Contributor

Choose a reason for hiding this comment

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

Wouldn't the "about-to-be-released" version have a greater version number than the "previous" one? (Or am I missing something here?)

@jkeenan
Copy link
Contributor

jkeenan commented Feb 12, 2026

We should get some feedback from recent or upcoming release managers as to whether this Porting program would be useful.
@richardleach @karenetheridge @thibaultduponchelle @steve-m-hay

@richardleach
Copy link
Contributor

Assuming I remember, I'll try it out next week.

@richardleach
Copy link
Contributor

I tried out the script and it was helpful.

I've not (yet) tested to see what happens to version numbers in the generated pod when make-rmg-checklist is run.

@jkeenan
Copy link
Contributor

jkeenan commented Feb 20, 2026

I tried out the script and it was helpful.

I've not (yet) tested to see what happens to version numbers in the generated pod when make-rmg-checklist is run.

That's good to know. My recommendation is: Take your time. We don't need to include it in today's release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Infrastructure Things needed to maintain Perl development

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants