Add the possibility to avoid the shebang at the start of the file
Phars can be used also as application served by webservers. In this case the shebang line is rendered on screen and this should be avoided in those (rare) cases.
Another possibility is to allow a custom stub.
"Fixed" this with #25
Thanks @giacmir for the suggestion and @ElectroLutz for the PR.
I left the issue open to keep the idea of custom stub. (I have to figure out some example cases that worth the implementation)
@MacFJA would a custom stub that just displays version info about a package be an idea?
@RyanMagnusson Something like:
- Generate a stub file with a comment in it that contains the version number (generated at the event
command.package.start) - Indicate in the composer.json where the file will be
- Use this file as the stub
That could be doable. And we can imagine that PharBuilder will come with predefined stub (with or without shebang for example)