| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
I recently added some tests to Install.t to check that files weren't
writeable. I used "-w $file", which gives a false positive if run as
root. So this commit changes the test to do a stat then test (mode & 0200);
hopefully that emulation on non-POSIX platforms is good enough for this to
be a valid test. perlport makes no mention of what stat->mode contains
on non-POSIX platforms.
(Chris fixed this this with 84d7dacc0cf1f by skipping the test if running
as root, but the current commit is more robust, in that is still tests for
correctness under root.)
|
| |
|
|
| |
Bump ExtUtils::Install to 1.66
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[perl #72028]
When upgrading an already-installed file, ExtUtils::Install could mess up
the permissions of files if the old versions of files were hard or
symbolic links. For example, if the Foo module had been installed as
lib/Foo.pm and for some reason (perhaps due to OS packaging) that file was
hard-linked to other/Foo.pm or replaced with a symbolic link to
other/Foo.pm, then when trying to install a newer release of Foo, the
permissions of the other/Foo.pm file could end up messed up.
This was due to ExtUtils::Install changing the permissions of the old file
before unlinking it; if the file was a link, then the linked file would
get the chmod instead. Since on POSIXy platforms it is the directory
permissions, not the file permissions, that affect whether a file can be
unlinked, the chmod was redundant anyway. So on these platforms, skip the
chmod.
I've also added tests for symlinked and hard-linked files.
|
| |
|
|
|
|
|
|
|
|
| |
This feature depended on test directories created on the fly being
in a predictable location, but as of 80af860fb39a3c6 they no longer
are. VMS systems released in the last 15 years or so don't even
need the feature, so the best path forward is to get rid of it.
A corresponding change was made in ExtUtils::MakeMaker 6.79_01 but
ExtUtils::Install maintains its own fork of the same test libraries.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
The toolchain is not installed on the target when cross-compiling.
So, this test must be skipped, see patch below.
(same problem as RT#119769 and RT#120398)
For: RT #120615
|
| | |
|
| | |
|
| |
|
|
| |
Bump $VERSION.
|
| |
|
|
|
| |
These were all uncovered by the new Pod::Checker, not yet in core.
Fixing these will speed up debugging the new Checker.
|
| |
|
|
|
|
|
|
|
|
| |
This reverts the code (but not test) portions of 3d55b451d9544fb.
The old solution of using catdir rather than a combination of
catdir and catpath works with and without extended filespecs
enabled, so there's no reason to maintain two versions, and thus
no reason to have all the boilerplate feature checking code at
the beginning of the module.
|
| | |
|
| | |
|
| |
|
|
| |
I think. I haven’t actually tested it.
|
| | |
|
| |
|
|
| |
Fixes cpan bug #50315.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
With this new parameter, the current directory is not included in the
installed module search. This avoids finding modules from other perls
which happen to be below the current directory.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
# New Ticket Created by (Peter J. Acklam)
# Please include the string: [perl #81888]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=81888 >
Signed-off-by: Abigail <abigail@abigail.be>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Broken in fc5e5837c991d3d3224259ff5c1d728d4e0636e2.
On VMS we were getting:
$ perl -"MConfig" -e "print join('+',split $Config{path_sep}, 'foo|bar|baz');"
f+o+o+|+b+a+r+|+b+a+z
which is a *lot* more pieces than we want. What was intended was:
$ perl -"MConfig" -e "print join('+',split quotemeta($Config{path_sep}), 'foo|bar|baz');"
foo+bar+baz
No version bump as this is test infrastructure and 1.55 has not been
released outside of development releases of blead.
|
| | |
|
| |
|
|
| |
We're testing from one level deeper than when we were in lib/.
|
| | |
|
| |
|
|
|
|
|
|
| |
In the core, @INC already contains the moral equivalent of blib/lib. However,
it's a relative path (by default), so make it absolute. It's easier to KISS if
this is done *before* any change of directory, so document this, and change the
non-core case to add the absolute path of 'blib/lib' to @INC, rather than the
absolute path of '../blib/lib'.
|
| | |
|
| |
|
