Closed
Description
@caskroom/maintainers This replaces #9203. Everyone agrees shim scripts are desirable, so lets allow them.
On a first phase, if anyone submits a cask that employs a shim script (usually inside a preflight
and using ruby methods to write to a file), we should (after determining it is indeed necessary and we have no other way to fix the problem) accept it and add a comment mentioning it’s a shim (this will allow us to find them easier to study/replace).
On a second phase (the point of this issue), we should implement something to make those easier to make. So, two points:
- Should we really implement something to make them easier, or should we just accept them in their usual rough form (has the advantage of not encouraging them, which is good since they should be used as a last resort)?
- Any suggestions for implementations/interface?