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. eg openrcAUR

Package naming

For init scripts, use modulename-init.

example bluetooth-openrcAUR jellyfin-runitAUR

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 it's init ie apparmor-openrcAUR requires openrc for it to work

Example packages

This article is issued from ArchWiki. The text is available under GNU Free Documentation License 1.3 or later unless otherwise noted. Additional terms may apply for the media files.