How riderius/aur works
Project type and purpose
• This is neither a “full-stack app” nor an “open-source library” in the traditional sense; it’s a monorepo of Arch User Repository (AUR) packages.
• Each top-level directory (e.g., aces, dict-dalf, git-fame, etc.) is an independent AUR package containing its build manifest (PKGBUILD), metadata (.SRCINFO), and optional install scripts or desktop entries.
• The repo’s purpose is to maintain and version‐control multiple AUR packages in one place.
File structure
• Top‐level: a README.md plus one directory per package.
• Inside each package folder:
• PKGBUILD – the build script for makepkg
• .SRCINFO – metadata derived from PKGBUILD for AUR
• optional files: .gitignore, *.install, .desktop files, .nvchecker.toml
• No “src” or “lib” code: the contents are pure packaging artifacts.
• No CI or deployment scripts present (though you could integrate a CI pipeline later to auto‐update .SRCINFO or run checks).
README for additional insights
• README simply states: “This repository contains log of my aur packages.”
Detail without overthinking
• Which packages have extra files (e.g., dict-jargon has .gitignore; pyannotate has .nvchecker.toml).
• You don’t have to show every file inside each module—focus on the common pattern (PKGBUILD + .SRCINFO) and call out exceptions.