(Rewrap; argh.) |
|||
| Line 1: | Line 1: | ||
=== General Naming === | === General Naming === | ||
tarball, project name from which this software came, and what has been used for | 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, | |||
follow those examples, however, as package names should strive to be consistent | 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 | Additionally, it is possible that the upstream name does not fall into the | ||
Revision as of 16:51, 18 June 2015
General Naming
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.