Checking for install triggered broken ags to start
On branch development Your branch is up to date with 'origin/development'. Changes to be committed: modified: install-scripts/ags.sh
This commit is contained in:
@@ -45,16 +45,9 @@ set -eo pipefail
|
|||||||
LOG="Install-Logs/install-$(date +%d-%H%M%S)_ags.log"
|
LOG="Install-Logs/install-$(date +%d-%H%M%S)_ags.log"
|
||||||
MLOG="install-$(date +%d-%H%M%S)_ags2.log"
|
MLOG="install-$(date +%d-%H%M%S)_ags2.log"
|
||||||
|
|
||||||
# Check if AGS is installed
|
# NOTE: We intentionally do NOT run `ags -v` here, because a broken AGS
|
||||||
if command -v ags &>/dev/null; then
|
# installation (missing GUtils, etc.) would crash gjs and spam errors
|
||||||
AGS_VERSION=$(ags -v | awk '{print $NF}')
|
# during install. We always (re)install v1.9.0 when this script is run.
|
||||||
if [[ "$AGS_VERSION" == "1.9.0" ]]; then
|
|
||||||
printf "${INFO} ${MAGENTA}Aylur's GTK Shell v1.9.0${RESET} is already installed. Skipping installation."
|
|
||||||
printf "\n%.0s" {1..2}
|
|
||||||
exit 0
|
|
||||||
fi
|
|
||||||
fi
|
|
||||||
|
|
||||||
# Installation of main components
|
# Installation of main components
|
||||||
printf "\n%s - Installing ${SKY_BLUE}Aylur's GTK shell $ags_tag${RESET} Dependencies \n" "${NOTE}"
|
printf "\n%s - Installing ${SKY_BLUE}Aylur's GTK shell $ags_tag${RESET} Dependencies \n" "${NOTE}"
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user