Porting/makerel no longer massages win32 files during the final tarball 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.

diff --git a/Porting/makerel b/Porting/makerel
index 5e7a362..e4dfdef 100644 (file)
--- a/Porting/makerel
+++ b/Porting/makerel
@@ -170,30 +170,6 @@ my @writables = qw(
 system("chmod +w @writables") == 0
     or die "system: $!";
 
-print "Adding CRs to DOSish files...\n";
-# This list is also in curliff.pl.
-my @crlf = qw(
-    djgpp/configure.bat
-    README.ce
-    README.dos
-    README.symbian
-    README.win32
-    symbian/config.pl
-    symbian/makesis.pl
-    symbian/README
-    symbian/xsbuild.pl
-    win32/Makefile
-    win32/Makefile.ce
-    win32/ce-helpers/compile-all.bat
-    win32/ce-helpers/compile.bat
-    win32/ce-helpers/registry.bat
-    win32/distclean.bat
-    win32/makefile.mk
-);
-system("perl -pi -e 's/\\015*\\012/\\015\\012/' @crlf") == 0
-    or die "system: $!";
-print "\n";
-
 chdir ".." or die $!;
 
 my $src = (-e $perl) ? $perl : 'perl'; # 'perl' in maint branch