PHP package guidelines

This document covers the creation of PKGBUILDs for PHP libraries. The target audience of this document is intended to be packagers of PHP libraries. For PHP Web applications, see Web application package guidelines

Arch package guidelines

32-bitCLRCMakeCrossDKMSEclipseElectronFontFree PascalGNOMEGoHaskellJavaKDEKernelLispMesonMinGWNode.jsNonfreeOCamlPerlPHPPythonRRubyRustShellVCSWebWine

Package names

For modules the package name should begin with php- and the rest of the name should be constructed from the library name by converting it to lowercase and separate words with hyphens. For example the package name corresponding to File iterator will be php-file-iterator.

Package file placement

PHP packages should install files into /usr/share/php/. This path should be in the php.ini include_path or open_basedir directive in order to be able to include libraries files in PHP web applications.

Architecture

In most cases, the arch array should contain any because most PHP packages are architecture independent.

gollark: ... I only have 8GB of RAM here.
gollark: ~100 mods or so, which most people should be able to handle okay.
gollark: Who are you, and I would prefer a smaller one.
gollark: Can we not have a CC-ish server with a decent amount of mods *and* which actually sticks around?
gollark: Nope, it'll probably be disappearinated forever.
This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.