| |
|---|
| | documented at: |
|---|
| | |
|---|
| | https://www.tundraware.com/TechnicalNotes/Divorce-Your-Linux-Admin |
|---|
| | |
|---|
| | # How To Use The Makefile |
|---|
| | ## How To Use The Makefile |
|---|
| | |
|---|
| | This `makefile` handles both the bootstrapping and then the full release of |
|---|
| | a custom linuxbrew based toolset, installed at any location you wish |
|---|
| | (so long as you have write permission there). |
|---|
| | |
|---|
| | Before doing anything, edit the variables as the top of the `makefile` |
|---|
| | to reflect where you want the built tarballs to be exported, where you |
|---|
| | intend to install the tools, and what set of tools you want installed. |
|---|
| | |
|---|
| | ## Release Versioning |
|---|
| | |
|---|
| | Both the bootstrap and full build process create tarballs *and rename |
|---|
| | the tools directory* with a version stamp in the form, `YYYMMDD`. The |
|---|
| | idea is to allow multiple verisons of your toolsets to exist under |
|---|
| | `${INSTALLDIR}`. You simply create a symlink in that directory named |
|---|
| | `${TOOLS}` to point to the version you want. This makes certain |
|---|
| | automation use cases with `tsshbatch` or `ansible` somewhat simpler. |
|---|
| | |
|---|
| | |
|---|
| | ## Building The Bootstrap Image |
|---|
| | |
|---|
| |
|---|
| | |
