summaryrefslogtreecommitdiff
path: root/dist/ExtUtils-Manifest
Commit message (Collapse)AuthorAgeFilesLines
* Help ExtUtils::Manifest deal with VMS extended filespecs.Craig A. Berry2013-02-142-8/+10
| | | | | | | | | For one thing, if we're cleaning up filenames, lets put that code in the sub called 'clean_up_filename' rather than in manifind. And since the language of the MANIFEST is really Unix-format filespecs, convert to those. This becomes especially important in handling extended filespecs because unixification also unescapes escaped characters.
* Normalize VMS case handling in ExtUtils::Manifest.Craig A. Berry2012-11-111-4/+7
| | | | | Both manifind and maniread were not completely matching filesystem behavior when downcasing filenames.
* Bump ExtUtils::Manifest version due to commits 97bae9c5 and bf081550Chris 'BinGOs' Williams2012-01-151-1/+1
|
* Current VMS can handle filenames with spaces.Craig A. Berry2011-12-311-0/+2
| | | | | | If they are escaped and on an ODS-5 volume, that is. We then have to clean up all versions of the files created by a test we weren't running before.
* avoid some test-time warningsZefram2011-11-161-0/+1
|
* Upgrade ExtUtils::Manifest from version 1.59 to 1.60Florian Ragwitz2011-08-191-1/+1
|
* Clean up MANIFEST before creating a new one.Craig A. Berry2011-08-121-0/+1
| | | | | | | | | | | | This is a follow-up to e4ac890e26c, which changed behavior from appending to an existing MANIFEST to creating a new one. On VMS, that would give us multiple versions, which probably wouldn't matter except that the tests insist that there is one and only one copy of every file they've created and they only clean up the highest version. The easiest way to handle this is to make sure we clean up first before creating a new MANIFEST file.
* prevent mixing non-native and native newlines in manifest filesSandy Andy2011-08-062-11/+67
|
* Move ExtUtils-Manifest from cpan/ to dist/Florian Ragwitz2010-11-093-0/+1352
Randy Kobes passed away recently, so let's have p5p maintain it for now.