Package policies: Difference between revisions

From Alpine Linux
(→‎Package Names: kernel flavors)
m (added a short license section)
Line 1: Line 1:
= Alpine Linux Package Policies =
The Alpine Linux Package Policies describe some of the policies when creating packages.
 
This document describes some of the policies when creating packages.


== Package Names ==
== Package Names ==
Line 14: Line 12:
== Package versions ==
== Package versions ==
* Package versions are similar to gentoo.
* Package versions are similar to gentoo.
== Licensing ==
* The license of the program should be based on the licenses approved by the [http://www.gnu.org/philosophy/license-list.html#GPLCompatibleLicenses Free Software Foundation] or [http://www.opensource.org/licenses/ OSI].
* If you are unsure about the license, please ask in our [[IRC]] channel.

Revision as of 06:53, 7 December 2011

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 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 modules (not applications) are prefixed with py-. (i.e py-libxml2)
  • Kernels and 3rdparty modules should be suffixed with the kernel flavor. (i.e -grsec or -vserver)

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.