Yeah, I tend to agree that either executable or not, these common utility scripts may not need to be exposed to end user in sbin and bin folders. But it seems we must still make some of these scripts executable as they are not only called in other scripts, but also called in scala source code.
On 2013-9-17, at 8:35, Mike <[email protected]> wrote: > Shane Huang wrote: >> - low-level or internally used utility scripts, i.e. >> compute-classpath, spark-config, spark-class, spark-executor > > I'd like to see script broken out into shell functions in a common file > that gets "."-included in every script, where that makes sense. > Specifically, I gather that compute-classpath.sh isn't run except as a > subroutine, so no need to promote it as an executable.
