Init package guidelines

Arch package guidelines

---

32-bit – CLR – CMake – Cross – DKMS – Eclipse – Electron – Font – Free Pascal – GNOME – Go – Haskell – Java – KDE – Kernel modules – Lisp – Meson – MinGW – Node.js – Nonfree – OCaml – Perl – PHP – Python – R – Ruby – Rust - Security – Shell – VCS – Web – Wine

This document covers standards and guidelines on writing PKGBUILDs for init scripts, e.g. openrc^AUR.

Package naming

For init scripts, use modulename-init. For example: ananicy-cpp-openrc^AUR, ananicy-cpp-runit^AUR, ananicy-cpp-dinit^AUR, ananicy-cpp-s6^AUR.

Note The package name should be entirely lowercase.

Architecture

See PKGBUILD#arch.

A init script should be architecture-independent.

Depends

All scripts should depend on its init, i.e. ananicy-cpp-openrc^AUR requires openrc^AUR for it to work.