| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
| |
[DELTA]
1.826 25 Jan 2012
* t/db-btree.t - fix use of "length @array"
[RT ##74336]
|
| |
|
|
|
|
|
|
|
|
|
| |
[DELTA]
1.825 24 Jan 2012
* t/db-btree.t - fix use of "length @array"
[RT ##74336]
and [perl #108970]
|
| |
|
|
|
|
|
|
|
| |
[DELTA]
1.824 6 Aug 2011
* Amendments to tests to work in blead
[RT #70108]
|
| |
|
|
|
|
|
|
|
| |
[DELTA]
1.823 6 Aug 2011
* croak if attempt to freeze/thaw DB_File object
[RT #69985]
|
| |
|
|
|
|
|
|
|
| |
[DELTA]
1.822 12 March 2011
* Keep DB_File's warnings in sync with perl's
[rt.cpan.org #66339]
|
| |
|
|
|
|
|
|
|
| |
[DELTA]
1.821 10 January 2011
* Fixed typos & spelling errors.
[perl #81792]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
(Also XS, skipped on Win32 and VMS)
|
