How jakoolit/arch-hyprland works
Main Components
• Install Entry Points – Represent the primary scripts such as install.sh, auto-install.sh, and uninstall.sh. These serve as the “controller” initiating the installation or removal process.
• Script Modules (install-scripts) – This directory contains many small, purpose-specific scripts (e.g., 00-base.sh, 01-hypr-pkgs.sh, nvidia.sh, pipewire.sh, etc.). These modular scripts are called by the entry point scripts based on user choices and system properties.
• Assets Directory – Encompasses configuration files and resources (like zsh themes, Thunar file manager configurations, fastfetch configs, and GTK/SDDM theme files). They are used for theming, customization, and applying specific user configurations.
• Helper/Utility Functions – Included scripts like Global_functions.sh which provide common functionality across the install-scripts.
Relationships and Interactions
• If applicable, include decision points (like conditional checks for Nvidia vs. Nouveau, or choice between graphical login managers), which may lead to different script execution paths (this can be represented using diamonds or annotated conditional branches).
Architectural Patterns and Design Principles
• Modularity – Emphasize that the project is built with reusable and independent install-scripts. Each script handles a single responsibility, which makes the architecture highly modular.
• Sequential and Conditional Flow – The main installer acts as a coordinator, launching different scripts in sequence as well as branching based on system checks (e.g., installing pipewire while disabling pulseaudio).