we all fixed now i hope lmao

README.org

@@ -0,0 +1,42 @@
+#+TITLE: CBSH Arch Linux Repository
+#+DESCRIPTION: The Arch Linux Repository for all of my Customised variants of programs i use.
+#+AUTHOR: Cabooshy (Cameron Miller)
+
+
+* Adding the CBSH Repository to pacman
+Adding a Third Party Repo, such as my repo, is easy. Add the Following Lines to the end of your ~/etc/pacman.conf~:
+
+#+begin_example
+[cbsh-arch-repo]
+SigLevel = Required DatabaseOptional
+Server = https://gitlab.com/cbsh/cbsh-arch/$repo/-/raw/main/$arch
+#+end_example
+
+Pacman will complain that the PGP key is invalid or corrupted, this can be resolved by locally signing the imported key:
+
+=$ sudo pacman-key --lsign-key 94424B71F1A63D9D=
+
+Then Sync the repos and update your system using:
+
+=$ sudo pacman -Syyu=
+
+Followed By:
+
+=$ sudo pacman -S name-of-package=
+
+* Current Packages in this Repository:
+ - alacritty-cbsh
+ - kitty-cbsh
+ - doom-cbsh
+ - qtile-cbsh
+ - pikaur
+ - zsh-cbsh
+ - dmenu-scripts
+ - cbsh-sddm-theme
+
+** Suckless Programs:
+ - dmenu-cbsh  -- Custom build of the Suckless dmenu run prompt to match the CBSH desktop.
+ - st-cbsh -- Custom build of the Suckless Simple Terminal to match the CBSH desktop.
+
+** Where is the suckless configs?
+Suckless Programs are configured by modifying the program's source code and then recompiling the source with those changes. The repo installs binaries of these packages, but the source code is also placed onto your system should you want to customise and patch them even more than they are. The Source code is located in /opt, so for example, the source code for st would be located at /opt/st-cbsh.

build-db.sh

@@ -0,0 +1,52 @@
+#!/usr/bin/env bash
+#
+# Script Name: build-db.sh
+# GitLab: https://www.gitlab.com/cabooshyy/cbsh-arch-repo
+# Contributors: Cameron Miller
+
+# Set with the flags "-e", "-u","-o pipefail" cause the script to fail
+# if certain things happen, which is a good thing.  Otherwise, we can
+# get hidden bugs that are hard to discover.
+set -euo pipefail
+
+x86_pkgbuild=$(find ../cbsh-arch-pkgbuild/x86_64 -type f -name "*.pkg.tar.zst*")
+
+for x in ${x86_pkgbuild}
+do
+	    mv "${x}" x86_64/
+	        echo "Moving ${x}"
+	done
+
+	echo "###########################"
+	echo "Building the repo database."
+	echo "###########################"
+
+	## Arch: x86_64
+	cd x86_64
+	rm -f cbsh-arch-repo*
+
+	echo "###################################"
+	echo "Building for architecture 'x86_64'."
+	echo "###################################"
+
+	## repo-add
+	## -s: signs the packages
+	## -n: only add new packages not already in database
+	## -R: remove old package files when updating their entry
+	repo-add -s -n -R cbsh-arch-repo.db.tar.gz *.pkg.tar.zst
+
+	# Removing the symlinks because GitLab can't handle them.
+	rm cbsh-arch-repo.db
+	rm cbsh-arch-repo.db.sig
+	rm cbsh-arch-repo.files
+	rm cbsh-arch-repo.files.sig
+
+	# Renaming the tar.gz files without the extension.
+	mv cbsh-arch-repo.db.tar.gz cbsh-arch-repo.db
+	mv cbsh-arch-repo.db.tar.gz.sig cbsh-arch-repo-db.sig
+	mv cbsh-arch-repo.files.tar.gz cbsh-arch-repo.files
+	mv cbsh-arch-repo.files.tar.gz.sig cbsh-arch-repo.files.sig
+
+	echo "#######################################"
+	echo "Packages in the repo have been updated!"
+	echo "#######################################"

gitlab-ci.yml

@@ -0,0 +1,12 @@
+# You can override the included template(s) by including variable overrides
+# SAST customization: https://docs.gitlab.com/ee/user/application_security/sast/#customizing-the-sast-settings
+# Secret Detection customization: https://docs.gitlab.com/ee/user/application_security/secret_detection/#customizing-settings
+# Dependency Scanning customization: https://docs.gitlab.com/ee/user/application_security/dependency_scanning/#customizing-the-dependency-scanning-settings
+# Note that environment variables can be set in several places
+# See https://docs.gitlab.com/ee/ci/variables/#cicd-variable-precedence
+stages:
+- test
+sast:
+  stage: test
+include:
+- template: Security/SAST.gitlab-ci.yml