I could be wrong here, but I think the check is to make sure that tar doesn't set +x on Makefile.PL or Build.PL, thus forcing the user to run the proper version of perl instead of automagically running the perl that shebang points to. (Example: Makefile.PL says #!/usr/bin/perl, but you really want to run /home/jon/blead/bin/perl. Forcing you to type this out is "a good thing".)
I personally don't see the value of this, I always run perl Makefile.PL anyway. Do +x *.PL files cause problems with CPAN installs? (Or am I completely wrong in my interpretation of this test? :) Regards, Jonathan Rockway chromatic wrote: > On Wednesday 06 September 2006 02:53, Thomas Klausner wrote: > >> - buildtool_not_executable >> Check if the buildtool (Makefile.PL, Build.PL) are not executable >> (and thus need to be called with 'perl Build.PL' thereby specifying >> which exact version of Perl you want) > > I'm not sure of the value of this one; how does an author make the buildtool > executable on Windows, for example? I have the impression (not using > Windows) that users must always call the tool with 'perl Build.PL' on such > platforms. > > Am I mistaken? > > -- c
