Use a Git Submodule for _tools
#63
Conversation
(Using submodules is a better way to include a Git repository inside ano- ther than just doing a raw clone of the repository into the relevant folder, as before, seeing as I don't recall the latter ever being a good idea.) Keep using `_tools` as that folder, but also test its status as a submodule when checking for its existence.
This is required because `_tools` is explicitly listed in the repository's `.gitignore` file.
|
Per my second commit message, I added the ' |
|
I could (and likely should?) also make the first submodule check not emit: on first use (when said folder doesn't already exist) — probably by redirecting standard error to ' |
|
My experience with Git submodules is that they seem like a great idea, but are a stumbling block for new users...unless the build process does the checks for missing modules. And in this case it does. So, +1. |
|
The full repository's build script is actually a different file, naturally called ' |
See my commit message(s) for details. I could have changed the script to commit any new submodule changes, but
it doesn't seem thatthis subdirectory ismeant to be trackedexplicitly listed in the repository's '.gitignore' file.