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-bit – CLR – CMake – Cross – DKMS – Eclipse – Electron – Font – Free Pascal – GNOME – Go – Haskell – Java – KDE – Kernel – Lisp – Meson – MinGW – Node.js – Nonfree – OCaml – Perl – PHP – Python – R – Ruby – Rust – Shell – VCS – Web – Wine

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: PotatOS is Primarily Otiose Transformative Advanced Technology, Or Something.

gollark: <@!261154480433659914> PotatOS is more "OS"ey than other stuff then, since it actually ends up reimplementing half the BIOS for sandboxing reasons.

gollark: functional programming™

gollark: It would be better to actually teach coroutine basics, which you're sure to encounter if doing that sort of thing.

gollark: That's a bad example for actually explaining the mechanics of coroutines.

This article is issued from Archlinux. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.