The documentation is missing specification for Fedora package ID like alexandria-0.7.9-2.fc37.noarch, its fields, allowed values, parse rules and examples.
alexandria-0.7.9-2.fc37.noarch
As a result of missing spec it is impossible to refer to package name components in discussion in a consistent way, hard to write scripts that validate and parse IDs.
I'm sorry, but while it might be nice to have something like this somewhere, it's really out of scope for the packaging guidelines. The guidelines do include things like restrictions on the allowed character set in the package name, and a description of how to construct what goes in the Version: tag, but that wouldn't help you in writing a general parser because RPM accepts far more than our guidelines would allow.
Metadata Update from @tibbs: - Issue close_status updated to: nothingtodo - Issue status updated to: Closed (was: Open)
Did I understand you right that specification for naming Fedora packages is out of scope for the Fedora packaging guidelines?
I don't know why you decided to mention RPM here. I am speaking only about alexandria-0.7.9-2.fc37.noarch strings and nothing else.
I don't think this is specific to Fedora, though? It's the standard way to construct file names for RPM packages, as far as I know. The format looks something like %{name}-%{?epoch:%{epoch}:}%{version}-%{release}.%{arch} and you will most likely only see that full string as part of file names. It's not a "package ID". If anything, a package's "ID" in Fedora is just the name of the source package (i.e. the value of the Name tag in a spec file). And if you want to ID a specific build, then that's usually called a NVR or NEVR (name-version-release or name-epoch-version-release) - same format as before, just without the trailing .%{arch}.
%{name}-%{?epoch:%{epoch}:}%{version}-%{release}.%{arch}
Name
.%{arch}
No need to explain it. The issue is closed. Nobody will ever look for this information here.
Log in to comment on this ticket.