- Oracle makes it difficult to download the Java SE Development Kit as
an offline download because the license must be accepted first. The
JDK is important to have installed as several Homebrew apps require
it to exist first.
- This provides a prompt for checking that the Java SE Development Kit
has been installed before proceeding as the original way of
installing it assumed you had visited the Oracle web site and
accepted the license.
The install-all command does not reflect that the `bin/install_homebrew` file was split into `bin/install_homebrew_formulas` and `bin/install_homebrew_casks`, and therefore fails to install.
- Discovered some applications, packaged in zip file format, would
extract to a sub-directory. This was problematic because all zip app
installs previously assumed the app would be unzipped in the current
directory. This fixes that situation where an app might be located in
a sub-directory or several sub-directory deep.
- The easiest fix for this problem would have been to the `-j` option
for *junk* paths via unzip: "The archive's directory structure is not
recreated; all files are deposited in the extraction directory (by
default, the current one)." ...but some zip files, when unzipped, run
executable code that creates the sub-directory structure dynamically
which makes the `-j` option not viable.
- The solution used to fix this problem uses `find` to determine if the
application to install is in a sub-directory. If so, then the app is
copied to the root folder (i.e. $MAC_OS_WORK_PATH) so the script can
install as it has done in the past. Because the file copy is executed
only if `find` finds something, this makes the copy optional for sub-
directories and is a no-op for standard zip files with no sub-
directories.
Discovered that some zip app downloads use executable scripts to
build for the particular machine when unzipped.
http://earthlingsoft.net/UnicodeChecker/index.html
- These scripts default to calling out to scripts of the same name as
defined by the custom configuration project (i.e.
`$MAC_OS_CONFIG_PATH`).
- This helps ensure the scripts in this project can be run
appropriately even if the custom configuration project hasn't fully
implemented all scripts yet.
- This also helps illustrate what scripts are necessary when creating a
custom configuration.
- Improves loading of the correct Bash environment/version, especially
on systems that might not be using a standard install (i.e.
Homebrew), by loading a version of Bash as defined by the environment
rather than a hard coded path.
[ci skip]
- This is a copy of the [OSX](https://github.com/bkuhlmann/osx) project
originally released on 2012-03-31. The OSX project has been
deprecated. All future development and support will take place with
this project instead.
- This project uses the *macOS* name in order to better match the
updated branding and terminology used by Apple.
