Create expected canonical structure per target system

It would be great for installation scripts to generate a canonical structure that follows the norms of the target system (e.g., Debian Linux, Mac OS X) regarding annotations, configuration, executables (including the paths of runtime primitives) and other components. This would also help in packaging PaSh for a variety of package managers and associated repositories (`apt-get`, `brew`, etc.). We probably need outside (per target-system) expertise for this.

Start by inventorying the installation scripts and comparing the requested annotations, configuration, executable locations, and runtime primitive paths across Debian Linux and Mac OS X. Then assess how the resulting layouts would support apt-get and brew packaging. Done means an agreed canonical structure and a defined plan for target-system-specific installation and packaging.

Written by the indexing model from the issue text.