My personalized Arch Linux distribution https://arch.p1st.de
Go to file
2021-05-02 19:25:48 +02:00
pkg test 2021-05-02 19:25:48 +02:00
prototype add nano 2021-04-29 15:15:08 +02:00
.gitignore rename $pkgname.install to .install 2021-04-29 14:24:28 +02:00
build-archiso.sh installer script: work in progress (8) 2021-05-01 17:04:27 +02:00
build-pkg.sh test 2021-05-02 19:25:48 +02:00
LICENSE Update 'LICENSE' 2021-04-20 10:09:13 +02:00
README.md installer script: work in progress (8) 2021-05-01 17:04:27 +02:00

My personalized Arch Linux packages

Some notes

Managing custom packages; managing a remote repository

  1. One could use crema
  2. 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

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

install -Dm0644 systemd.preset "$pkgdir"/usr/lib/systemd/system-preset/"$pkgname".preset

Example package: