(Original text) |
No edit summary |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=== General Naming === | === General Naming === | ||
In the absence of specific guidelines relating to the type of software you are | |||
packaging, package names should be in lower case and uses dashes in preference | |||
to underscores. You can take some cues from the name of the upstream tarball, | |||
project name from which this software came, and what has been used for this | |||
package by other distributions/packagers in the past. You can also request | |||
guidance from the upstream developers. Do not just blindly follow those | |||
examples, however, as package names should strive to be consistent within | |||
Fedora more than consistent between distributions. | |||
Also remember to check whether the type of package you are packaging has specific rules for naming. [[Packaging:NamingGuidelines#Font_Packages |Font packages]] and the various sorts of [[Packaging:NamingGuidelines#Addon_Packages_.28General.29 |addon packages]], for instance. | Additionally, it is possible that the upstream name does not fall into the | ||
[[#CommonCharacterSet| Common Character Set]] . If this is the case, refer to: | |||
[[#Transliteration| When Upstream Naming is outside of the specified character | |||
set]] . | |||
Also remember to check whether the type of package you are packaging has | |||
specific rules for naming. [[Packaging:NamingGuidelines#Font_Packages |Font | |||
packages]] and the various sorts of | |||
[[Packaging:NamingGuidelines#Addon_Packages_.28General.29 |addon packages]], | |||
for instance. | |||
Latest revision as of 20:54, 18 June 2015
General Naming
In the absence of specific guidelines relating to the type of software you are packaging, package names should be in lower case and uses dashes in preference to underscores. You can take some cues from the name of the upstream tarball, project name from which this software came, and what has been used for this package by other distributions/packagers in the past. You can also request guidance from the upstream developers. Do not just blindly follow those examples, however, as package names should strive to be consistent within Fedora more than consistent between distributions.
Additionally, it is possible that the upstream name does not fall into the Common Character Set . If this is the case, refer to: When Upstream Naming is outside of the specified character set .
Also remember to check whether the type of package you are packaging has specific rules for naming. Font packages and the various sorts of addon packages, for instance.