| |
@@ -248,6 +248,12 @@
|
| |
https://www.python.org/dev/peps/pep-0503/#normalized-names[PEP 503],
|
| |
and <<py_dist_name,the `+%{py_dist_name}+` macro>> implements it
|
| |
for Fedora packaging.
|
| |
+ The canonical name is obtained by switching the project name to lower case
|
| |
+ and converting all runs of non-alphanumeric characters to single “-” characters.
|
| |
+ Example: “The $$$ Tree” becomes “the-tree”.
|
| |
+
|
| |
+
|
| |
+
|
| |
|
| |
Elsewhere in this text,
|
| |
the metavariable `+DISTNAME+` refers to the canonical form of the project name.
|
| |
@@ -284,7 +290,7 @@
|
| |
The Fedora package’s name *SHOULD* contain
|
| |
the <<Canonical project name>>.
|
| |
If possible, the project name *SHOULD* be the same
|
| |
- as the name of the main importable module,
|
| |
+ as the name of the main importable module, in lowercase
|
| |
with underscores (`+_+`) replaced by dashes (`+-+`).
|
| |
|
| |
If the importable module name and the project name do not match,
|
| |
Explain how canonical names are created.
We ran into the canonical name not being very clear in https://bugzilla.redhat.com/show_bug.cgi?id=2139873.
The text used to be in the old Fedora packaging guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/Python_201x/#_automatic_provides_with_a_standardized_name