Package policies: Difference between revisions
Funkyfuture (talk | contribs) (clarification concerning python libraries) |
m (Added internal link to TODO:py3 packages) |
||
| Line 8: | Line 8: | ||
* Perl modules (not applications) are prefixed with ''perl-''. (i.e perl-xml-parser) | * Perl modules (not applications) are prefixed with ''perl-''. (i.e perl-xml-parser) | ||
* Python 2 modules (not applications) are prefixed with ''py-''. (i.e py-libxml2) | * Python 2 modules (not applications) are prefixed with ''py-''. (i.e py-libxml2) | ||
* Python 3 modules (not applications) are prefixed with ''py3-''. (i.e py3-libxml2) | * [[TODO:py3 packages|Python 3]] modules (not applications) are prefixed with ''py3-''. (i.e py3-libxml2) | ||
* Kernels and third party modules should be suffixed with the kernel flavor. (i.e ''-grsec'' or ''-vserver''). | * Kernels and third party modules should be suffixed with the kernel flavor. (i.e ''-grsec'' or ''-vserver''). | ||
# Don't use ''-'' sign in kernel flavor name. | # Don't use ''-'' sign in kernel flavor name. | ||
Revision as of 22:53, 18 September 2017
The Alpine Linux Package Policies describe some of the policies when creating packages.
Package Names
- All package names should be lowercase.
- Development files are placed in subpackages with -dev suffix (i.e uclibc-dev)
- Documentation files (incl. man pages) are placed in subpackages with -doc suffix (i.e expat-doc)
- Lua modules (not applications) are prefixed with lua-. (i.e lua-posix)
- Perl modules (not applications) are prefixed with perl-. (i.e perl-xml-parser)
- Python 2 modules (not applications) are prefixed with py-. (i.e py-libxml2)
- Python 3 modules (not applications) are prefixed with py3-. (i.e py3-libxml2)
- Kernels and third party modules should be suffixed with the kernel flavor. (i.e -grsec or -vserver).
- Don't use - sign in kernel flavor name.
- Specify KERNEL_FLAVOR_DEFAULT as your kernel flavor, if you want boot your kernel by default.
Package versions
- Package versions are similar to gentoo.
Licensing
- The license of the program should be based on the licenses approved by the Free Software Foundation or OSI.
- If you are unsure about the license, please ask in our IRC channel.