| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
The message emitted just before creating the .xz file was identical
to the message emitted just before creating the .gz file. Which
didn't make much sense.
|
| |
|
|
|
|
|
|
|
|
|
| |
xz compresses better and decompresses faster, gzip is still more
compatible and uses less memory. In the recent years we've
archived perl as both gzip, bzip2 and xz which doesn't make much
sense. This is a followup to f276fdad.
closes [perl #132381].
|
| |
|
|
|
|
|
| |
It was decided at the perl core hackathon in October 2017 to go ahead
and do this.
|
|
|
|
|
|
|
|
|
|
| |
Switch from two-argument form. Filehandle cloning is still done with the two
argument form for backward compatibility.
Committer: Get all porting tests to pass. Increment some $VERSIONs.
Run: ./perl -Ilib regen/mk_invlists.pl; ./perl -Ilib regen/regcharclass.pl
For: RT #130122
|
|
|
|
|
|
|
|
|
|
|
| |
autodie's utime.t touches touch_me, in a git checkout that's fine
since the file is writable, but in a distribution, all files are
read-only by default, and on Win32 the utime() call the test expects
to succeed fails.
Per Sisyphus's note, also make win32/GNUmakefile writable to match the
other Win32 makefiles, since they're often modified to configure the
build.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
With the default of -6 produced much smaller tarball than
.gz (7z produced) and .bz2
-rw-r--r-- 1 bingos bingos 13601234 Sep 29 20:07 perl-5.21.5.tar.bz2
-rw-r--r-- 1 bingos bingos 15699515 Sep 29 20:07 perl-5.21.5.tar.gz
-rw-r--r-- 1 bingos bingos 10982580 Sep 29 20:08 perl-5.21.5.tar.xz
It's an option if we ever need it.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Add rules to the Win32 Makefiles to call utils/Makefile.PL to generate
utils/Makefile, and rules to both them and the *nix Makefile to delete
the generated file as part of the cleanup targets.
VMS continues to do its own thing, rather than using utils/Makefile.
|
| |
|
| |
|
|
|
|
|
|
| |
(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.)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
For some time now (I suspect since 691ce773f), makerel has always tried
to build releases as perl-5.x.y-uncommitted.tar.gz. This always
confuses and/or panics new release engineers, who see the error before
the "don't worry, use -s ''" advice in the RMG.
This change just makes makerel skip the usually-#ifdef-ed-away line that
is getting that -uncommitted. makerel still picks up other
locally-applied patches, but will skip uncommitted.
|
| |
|
| |
|
|
|
|
|
| |
Most Win32 shell environments take no notice of these permissions
anyway, but this seems like a safer option than removing them all.
|
|
|
|
|
| |
Remove support for the Borland C++ compiler on Win32, as agreed here:
http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2011-09/msg00034.html
|
|
|
|
|
|
|
|
| |
global.sym was a file listing the exported symbols, generated by regen/embed.pl
from embed.fnc and regen/opcodes, which was only used by makedef.pl
Move the code that generates global.sym from regen/embed.pl to makedef.pl,
and thereby eliminate the need to ship a 907 line generated file.
|
|
|
|
|
|
|
| |
It automatically will use these to create archives ~5% smaller,
otherwise falls back to gzip and bzip2.
Also, document in Porting/release_managers_guide.pod.
|
|
|
|
|
|
|
|
|
|
|
| |
Previously perl.h contained a long section of MGVTBL_SET() macros declaring
the core's various magic vtables. Convert the information into data structures
in a new script regen/mg_table.pl, and use this to generate a new file
mg_vtable.h, included by perl.h
This is the first step in reducing the number of places that data relating to
magic vtables is declared (and has to be kept in sync), and will allow more
flexibility in parts of the core's implementation.
|
|
|
|
|
|
|
|
| |
As it and Perl_yylex() both need FEATURE_IS_ENABLED, feature_is_enabled() is
no longer static, and the two macro definitions move from toke.c to perl.h
Previously, one had to cut and paste the output of perl_keywords.pl into the
middle of toke.c, and it was not clear that it was generated code.
|
|
|
|
|
|
|
|
|
|
|
| |
Eliminate the #define pp_foo Perl_pp_foo(pTHX) macros, and update the 13
locations that relied on them.
regen/opcode.pl now generates prototypes for the PP functions directly, into
pp_proto.h. It no longer writes pp.sym, and regen/embed.pl no longer reads
this, removing the only ordering dependency in the regen scripts. opcode.pl
is now responsible for prototypes for pp_* functions. (embed.pl remains
responsible for ck_* functions, reading from regen/opcodes)
|
|
|
|
|
|
|
|
|
| |
# New Ticket Created by (Peter J. Acklam)
# Please include the string: [perl #81910]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=81910 >
Signed-off-by: Abigail <abigail@abigail.be>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When rolling a release on Windows it is useful to use the Cygwin tools, but
the chmod command doesn't honour the user's umask when operating outside of
the Cygwin bash shell. For example, with a umask of 0022 and a file having
permissions 0400, one would expect "chmod +w" to change the file's
permissions to 0600. It does inside the Cygwin bash shell, but inside the
standard Windows command prompt it changes the file permissions to 0622
instead.
The problem is avoided by using "chmod u+w" instead to be sure that we only
set the write-bit for the owner user.
Note that the PAUSE indexer now detects uploads containining world writable
files or directories and will not index them. In such cases, it generates
new tarballs with "-withoutworldwritables" injected into the names and
indexes those instead of the original uploads. We do not want this
happening to perl distributions!
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the course of releasing perl-5.11.5 I found a few things that are not
quite correct or no longer relevant:
- Add comments on the problems with doing this on Win32
- There are no longer Roman numerals in README.vms (since eb505c2afb6b5ac2aaba7935878ae6494d44732a)
- Note that Module::CoreList's Changes and META.yml files need updating too
- Fix Porting/makerel's null device redirection
One bigger problem remains to be resolved: when run in a normal cmd.exe
shell on Win32, the Porting/makerel script currently generates tarballs
containing world-writable files and directories, which the PAUSE indexer
then rejects as a possible security risk.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
build process
I _believe_ that this change will mean that our shipped tarball will
contain all files exactly as they are in the repo - The only difference
will be in file permissions.
I'm told that git can version the execute bit on files. If I'm feeling
especially adventurous, I may write a porting test to ensure that the
right files (and only the right files?) are marked +x in git and then
remove that bit from Porting/makerel. I wouldn't mind it if someone beat
me to that.
|
| |
|
| |
|
| |
|
|
|
|
| |
and be quieter on failure
|
|
|
|
| |
gives you sha1 sums of the built distribution
|
| |
|
|
|
|
|
|
| |
* add cmd-line switches
* make ExtUtils::Manifest silent
* remove some autogenerated files from the fixup list
|
|
|
|
|
| |
(Ignore .git directory, .gitignore files, and references to removed perforce
related scripts.)
|
|
|
|
| |
It has its tentacles in many other places.
|
|
|
|
|
| |
(thanks to Sébastien Aperghis-Tramoni)
p4raw-id: //depot/perl@32495
|
|
|
|
|
|
|
|
|
|
|
| |
exterminated file, one file that is now a dummy, and adding in various
files that are actually read/write because they are regenerated from
source files. Change the type of regcharclass.h to read/write in
Perforce as it is auto-generated. (And all other auto-generated files
are read/write. There's some irony here - the only read/write files
are the ones you shouldn't edit. All the ones you can edit are read
only.)
p4raw-id: //depot/perl@32427
|
|
|
|
|
|
|
|
| |
Message-ID: <46F063E0.1000004@iki.fi>
(Restores a pre-generated utils/Makefile for the benefit of Win32,
which can't run utils/Makefile.SH itself)
p4raw-id: //depot/perl@31899
|
|
|
|
|
| |
"used only once" warning.
p4raw-id: //depot/perl@30178
|
|
|
|
|
| |
Message-ID: <B356D8F434D20B40A8CEDAEC305A1F2453D653@esebe105.NOE.Nokia.com>
p4raw-id: //depot/perl@24271
|