Among the many *.pike (and *.pmod!) files in the module directories there are a few marked as executable but missing a shebang (#!) line, and a few that has a shebang but are not executable. Which ones, if any, are meant to be executed directly? (I'm not talking about scripts that used in the build process, only ones that are installed.)
Since none are installed as general-purpose tools in $PATH, and since the ones in Tools.Standalone are meant to be run via pike -x, couldn't you simply delete all the shebangs (which, in case they read "#!/usr/local/bin/pike", are wrong anyway if pike isn't installed under /usr/local) and reset the x bits?
As you can run all of those files with "pike <file>" I really see no point in having #! in them. I don't see how they are in the way either though. I think executable flags are just mistakes, which are difficult to handle by CVS.
Well, Lintian (the Debian policy conformance checker) complains when there is a mismatch between executability and shebang-havingness.
I can see why the standalone files have it. So that you can pull one out, rename it to something without .pike and mark it as executable. If Debian wants to strip all #! and set all files non-executable in the library tree, I have no objections.
pike-devel@lists.lysator.liu.se