PHP package guidelines: Difference between revisions

From ArchWiki
(Update Interlanguage link)
 
(One intermediate revision by one other user not shown)
Line 7: Line 7:
This document covers the creation of [[PKGBUILD]]s 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]]
This document covers the creation of [[PKGBUILD]]s 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]]


=== Package names ===
== Package names ==


For modules the package name should begin with {{ic|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 {{ic|File iterator}} will be {{ic|php-file-iterator}}.
For modules the package name should begin with {{ic|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 {{ic|File iterator}} will be {{ic|php-file-iterator}}.


=== Package file placement ===
== Package file placement ==


PHP packages should install files into {{ic|/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 apps.
PHP packages should install files into {{ic|/usr/share/php/}}. This path should be in the {{ic|php.ini}} {{ic|include_path}} or {{ic|open_basedir}} directive in order to be able to include libraries files in PHP web applications.


=== Architecture ===
== Architecture ==


In most cases, the {{ic|arch}} array should contain {{ic|'any'}} because most PHP packages are architecture independent.
In most cases, the {{ic|arch}} array should contain {{ic|any}} because most PHP packages are architecture independent.

Latest revision as of 08:20, 8 July 2022

Arch package guidelines

32-bitCLRCMakeCrossDKMSEclipseElectronFontFree PascalGNOMEGoHaskellJavaKDEKernelLispMesonMinGWNode.jsNonfreeOCamlPerlPHPPythonRRubyRustShellVCSWebWine

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

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.