| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Other things being equal, Porting/core-cpan-diff defaults to passing '-u
--binary' to the 'diff' command. It turns out that, though '--binary'
is not a *documented* option for GNU diff, it is present in the source
code (rjbs research in
https://github.com/Perl/perl5/pull/19027#issuecomment-898901007). The
'--binary' option clearly does *not* work on FreeBSD and probably
doesn't work on other *BSDs. On those systems, running the program
spews more than 80,000 lines of error output.
Code revised to remove '--binary' on *BSDs. Documentation adjusted.
For https://github.com/Perl/perl5/pull/19027
|
|
|
|
|
|
|
|
| |
Turning off -b (ignore whitespace) revealed a whitespace difference lurking
in blead's copy of a NEXT test file, which there is no need for.
Turning on --binary revealed EOL differences in numerous Win32API-File
files. Hopefully a future CPAN release will fix those since the files in
its GitHub repo match blead as far as EOLs go already.
|
|
|
|
|
|
|
|
|
| |
It uses 'Perl:', not 'perl:', a few lines later.
(We currently have "found more than one CPAN candidate" for libnet, which
I have addressed by scheduling the removal of old versions from CPAN: 1.29
was the last version containing some packages, so it remained in
02packages.details.txt because of that.)
|
|
|
|
|
|
|
| |
Allow -v with -x
Show diff for customized scripts when -d and -v
Allow -v #
Set -d if -v 3 and up
|
|
|
|
|
| |
Also add extra verbose output to Porting/core-cpan-diff to identify such
cases.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Note:
Porting/core-cpan-diff refactored to use Archive::Tar
instead of Archive::Extract
|
| |
|
| |
|
|
|
|
| |
otherwise Memoize-1.03.tgz gets skipped.
|
| |
|
|
|
|
|
|
| |
(corelist.pl no longer uses curl, diffstat is no longer required to produce
the list of acknowledgements and 7z should be used to create smaller
tarballs. Also, core-cpan-diff no longer uses wget.)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
It was trying to download a test file that doesn't exist in minicpans.
|
|
|
|
|
| |
CPAN URL into its own subroutine: cpan_url_distribution()
in Porting/core-cpan-diff
|
|
|
|
|
|
|
| |
We have the CUSTOMIZED field in Maintainers.pl for indicating where we
expect blead to differ from a CPAN tarball. This commit documents that
in perlhack and makes core-cpan-diff more aggressive about checking it
and reporting about it.
|
| |
|
|
|
|
|
| |
Uses CUSTOMIZED in Maintainers.pl to also track files that only exist
in Perl and not on CPAN.
|
|
|
|
|
|
|
|
| |
The recent "Foo-Bar-1.23-withoutworldwriteables.tar.gz" dists are an example of
that. They'll extract to Foo-Bar-1.23/.
Caching of the untarred dists probably doesn't work for those dists, but at
least it works at all.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When porting/makerel runs, all files copied into the directory for the
tarball have the executable bit stripped and then only a specific set of
files have the executable bit restored.
There are many files in the repo that have the executable bit set in the
repo that will be stripped. So that the state of files in the repo is
as close as possible to the state of files in the release tarball, the
executable bit has been stripped from such files.
In one recent case, a file added from a dual-life module needed the
executable bit set. Because it had the bit in the repo but was
not listed in makerel to get an executable bit, tests using it
passed in the repo and failed in the tarball.
This commit refactors the list into a new file, Porting/exec-bit.txt
and add tests to detect a mismatch between files listed there
and actual executable bits in the repo.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Some dual-life modules have custom files in core that differ from
CPAN. (e.g. Makefile.PL in libnet) These files need to be listed
in EXCLUDED, but also in CUSTOMIZED so that we don't flag them
incorrectly as "only in Perl"
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Extracted directories are cached and re-used
* Perl vs CPAN version mismatches shown in summary output
* Various minor code cleanup
Some diagnostic output was surpressed in diff mode, but not all.
I found the output confusing to follow in diff mode as a result
so I enabled some of the previously surpressed output.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
and display.
(Also show module names being processed when using -o)
|
| |
|
|
|