mirror of
https://codeberg.org/privacy1st/arch
synced 2024-12-23 01:16:04 +01:00
My personalized Arch Linux distribution https://arch.p1st.de
pkg | ||
prototype | ||
.gitignore | ||
build-archiso.sh | ||
build-pkg.sh | ||
LICENSE | ||
README.md |
My personalized Arch Linux packages
Some notes
Managing custom packages; managing a remote repository
- One could use crema
- Or some self made shell scripts: pkg/de-p1st-repo/README.md
Notes about PKGBUILD
Package naming
Package names are prefixed with de-p1st
as this is one of my
domains (p1st.de) which itself is an abbreviation of
privacy1st.de
Creating config files
install -Dm644 $src $pkgdir/$dst
Example: pkg/de-p1st-sudo/PKGBUILD
Changing existing config files
holo
from the AUR- https://github.com/holocm/holo/blob/master/doc/holo-files.8.pod
install -Dm0544 some-config.conf.holoscript "$pkgdir"/usr/share/holo/files/"$pkgname"/etc/path/to/some-config.conf.holoscript
Example:
Home skeleton
Pacman should never change files in $HOME
. To still be able to include
customized configurations, one can copy them to the skeleton used for new users:
Files from /etc/skel
are copied to /home/$USER
when new users are created.
Example: pkg/de-p1st-gnupg/PKGBUILD
Enabling services
- systemd.preset - Service enablement presets
- man 5 systemd.preset
install -Dm0644 systemd.preset "$pkgdir"/usr/lib/systemd/system-preset/"$pkgname".preset
Example package: