Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clear up ambiguity with RPM epochs #70

Merged
merged 5 commits into from
Nov 19, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions README.rst
Original file line number Diff line number Diff line change
Expand Up @@ -667,13 +667,16 @@ candidate list further down.
- the `namespace` is the vendor such as fedora or opensuse
It is not case sensitive and must be lowercased.
- the `name` is the RPM name and is case sensitive.
- the `version` is the combined epoch (if not 0), version and release of an
RPM.
- the `version` is the combined version and release of an
RPM
- `epoch` (optional for RPMs) is a qualifier as it's not required for
unique identification, but when the epoch exists we strongly
encourage using it
- `arch` is the `qualifiers` `key` for a package architecture
- Examples::

pkg:rpm/fedora/[email protected]?arch=i386&distro=fedora-25
pkg:rpm/opensuse/[email protected]-1.1.?arch=i386&distro=opensuse-tumbleweed
pkg:rpm/[email protected]-1.el6?arch=i686&epoch=1&distro=fedora-25


Other candidate types to define:
Expand Down