Fork: 0
tundra / tools-builder
Browse code
break out logic to turn of https cert checking into separate make target
master
1 parent ec13b01 commit 6ac317af086aa8a59c97356f97cdb68a74ff1f48
@tundra tundra authored on 20 Dec 2020
Patch
Unified Split
Showing 2 changed files
View
10
■■■■■
 README.md
https://www.tundraware.com/TechnicalNotes/Divorce-Your-Linux-Admin
 
 
## How To Use The Makefile
 
NOTE: As of 12-20-2020 there is a new `make` target called `insecure`.
If you see a problem with `git clone` failing during builds, run `make
insecure` and this should fix it. This is caused by some problem with
how `openssl@1.1` finds its certs.
 
This "fix" works by telling both `curl` and `git` to ignore
certificate validation of https. So ... DON'T do this on a
production environment. It's really there for building inside containers
to produce release tarballs.
 
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).
View
6
■■■■■
 makefile
# Full tools set
 
full-build:
@echo "Make sure the bootstrap is installed at ${TOOLSDIR}"
echo insecure > ~/.curlrc
git config --global http.sslVerify false
sudo yum -y install autoconf automake patch perl texinfo
${BREW} install --verbose ${LANGS}
${BREW} link --verbose python
ln -nfs ${TOOLSDIR}/bin/python3 ${TOOLSDIR}/bin/python
brew update
brew upgrade
pip install ${PIPMODULES} -U --ignore-installed
 
insecure:
echo insecure >> ~/.curlrc
git config --global http.sslVerify false
 
 
# Housekeeping
 
push-release: