On 6/13/05, Steve Hay <[EMAIL PROTECTED]> wrote: > demerphq wrote: > > >On 6/13/05, H.Merijn Brand <[EMAIL PROTECTED]> wrote: > > > > > >>On Mon, 13 Jun 2005 15:41:41 -0400, vadim <[EMAIL PROTECTED]> wrote: > >> > >> > >>>I already have a patch. > >>>May be its not perfect. > >>> > >>> > >>I'll leave it to Steve > >> > >> > > > >Please could we not forget or overlook or otherwise warnock the issue > >of the /y flag on XCOPY and other aspects of the Win32 makefiles that > >are included only to be able to build on operating systems that MS no > >longer supports and has sent out End Of Life notices on? > > > >Does _anybody_ on this list build perl on pre win2k machines nowadays? > > > My own gut feeling is that building on Win9x/WinNT4 should still be > supported. If you drop support for building on old OS's then it's not > long before you also start dropping support for building with old > compilers, and even VC++ 6 is getting rather old now. 7 is out and 8 is > nigh if not out already. Before you know it, you won't be able to build > Perl with VC++ 6. That's already happened to Parrot (the last time I > tried, at least) and it really p***ed me off. I wouldn't want to see it > happen to Perl too. > > IIRC, Greg Matheson was on this list fairly recently, building Perl on > Win98. Others may be doing likewise, but not even on this list.
Ok, fine. So we cant go that route. Howsabout a different mechansim. We can replace the usage of XCOPY with a batchfile that acts as a wrapper to OSize the command, ie here is xcopyit.bat that i just put together: @echo off if "%OS%"=="" goto win95 ver | find "Version 5" >nul if errorlevel 1 goto NO_Y echo F|xcopy /y %* goto END :NO_Y echo F|xcopy %* goto END :WIN95 echo F|xcopy %1 %2 %3 %4 %5 %6 %7 %8 %9 :END We could even be cheeky and have the batch file rewrite itself with the correct usage for the OS it is first run on, but i beleive the above would resolve the outstanding issues with xcopy. Note also the echo trick prevents the "Does foo specify a file name or directory name on target" and can also be used for Y/N questions and answers too, but its critical no space is in between the F and the pipe symbol. If the echo F| trick isnt needed it causes a superfluous "The process tried to write to a nonexistant pipe" so its possible that we would better to have several versions of the script for the different usage requirements. Cheers, Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"
