From Fedora Project Wiki
(Rewrap; argh.)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
=== General Naming ===
 
=== General Naming ===
When naming a package 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  
+
In the absence of specific guidelines relating to the type of software you are
this package by other distributions/packagers in the past.  Do not just blindly  
+
packaging, package names should be in lower case and uses dashes in preference
follow those examples, however, as package names should strive to be consistent  
+
to underscores.  You can take some cues from the name of the upstream tarball,  
within Fedora more than consistent between distros.  You should generally use
+
project name from which this software came, and what has been used for this
lowercase and turn underscores into dashes unless there's a compelling reason
+
package by other distributions/packagers in the past.  You can also request
to follow a different upstream convention.  
+
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  

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.