== Versioning guidelines have moved

  This document previously contained information on both naming and versioning.

  == Common Character Set for Package Naming

  0123456789-._+

  ....

  on using the `+-._++` characters.

  === General Naming

  within Fedora more than consistent between distributions.

  Additionally, it is possible that the upstream name does not fall into the

  If this is the case, refer to:

  Also remember to check whether

  the type of package you are packaging

  has specific rules for naming.

  and the various sorts of

  for instance.

  === Separators

  The maintainer MUST NOT use an underscore '_', a plus '+', or a period '.' as a delimiter.

  Version numbers used in compat libraries do not need to omit the dot '.'

  or change it into a dash '-'

  for more info on this case).

  There are a few exceptions to the no underscore '_' rule.

  * httpd, pam, and SDL addon packages are excluded,

  * packages that are locale specific,

  and use the locale in the name are excluded,

  * Compat packages where the base package name ends in a digit.

  * packages where the upstream name naturally contains an underscore

  are excluded from this. Examples of these packages include:

  Conflicting package names,

  even if they differ by case alone,

  are not allowed.

  for more details.

  == Multiple packages with the same base name

  The exception to this is for perl module packaging.

  The CPAN Group and Type SHOULD be capitalized in the name,

  as if they were proper nouns.

  == Renaming/replacing existing packages

  == Documentation Subpackages

  Packages containing fonts must be named

  *[foundryname-]projectname[-fontfamilyname]-fonts*,

  in lowercase.

  == Addon Packages

  === GAP

  === gnome shell extensions

  used when importing it in Python scripts.

  This name will be prefixed depending on the type of the package.

  === Python source package naming

  === Sugar Activities

  The name for all packaged Sugar activities must be prefixed with sugar-.

  === Tcl/Tk extensions

  The name for all packaged Tcl/Tk extensions must be prefixed with tcl-.

  This rule applies even for Tcl/Tk packages

  that are already prefixed with tcl in the name.

  === locales