Closed johnramsden closed 5 years ago
Rather than pulling alez every time it's run, I think it makes sense to only clone the repo when there are changes. It would also be useful to do the initial clone during the build of the ISO and have it baked in meaning startup will be faster.
Run a shallow clone during the ISO build:
git clone --branch master --single-branch --depth 1 https://github.com/danboid/ALEZ.git ${ALEZ_BUILD_DIR}/iso/airootfs/usr/local/share/ALEZ
Upon running alez-downloader.sh, it checks if the git repo exists, and runs an update if it is needed. If the repo doesn't exist it will clone it.
alez-downloader.sh
Thanks John!
Summary
Rather than pulling alez every time it's run, I think it makes sense to only clone the repo when there are changes. It would also be useful to do the initial clone during the build of the ISO and have it baked in meaning startup will be faster.
implementation
Run a shallow clone during the ISO build:
Upon running
alez-downloader.sh
, it checks if the git repo exists, and runs an update if it is needed. If the repo doesn't exist it will clone it.Tests