This documentation page uses "ursine" to describe non-modular RPM content: https://docs.fedoraproject.org/en-US/modularity/architecture/consuming/upgrade-paths/
Standalone packages (also refered-to as "bare RPMs" or "ursine RPMs") — packages not being part of a module. In Fedora, these are coming from the Everything repository.
There were previous discussions that we should standardize on using "non-modular RPM" as the word "ursine" in relation to the English "bare" and "bear" homonym was not obvious and could be confusing for anyone whose first language is not English.
I am not sure where else this word may appear in the documentation, but I would ask that we consider changing this.
+1, replace all such references with "non-modular RPM".
$ git clone https://pagure.io/fedora-docs/modularity.git $ find ./modularity -type f -exec grep -Hi 'ursine' {} \; ./modularity/modules/ROOT/pages/architecture/consuming/dnf-behavior.adoc:* Ursine ("bare") packages are those that are not part of any module. ./modularity/modules/ROOT/pages/architecture/consuming/dnf-behavior.adoc:* Any package in an enabled module takes priority over any ursine RPM ./modularity/modules/ROOT/pages/architecture/consuming/dnf-behavior.adoc:* If there's an ursine or modular RPM with a higher NVR than the hotfix ./modularity/modules/ROOT/pages/architecture/consuming/dnf-behavior.adoc: one, the ursine or modular one wins. This is to ensure new proper ./modularity/modules/ROOT/pages/architecture/consuming/upgrade-paths.adoc:1. **Standalone packages** (also refered-to as "bare RPMs" or "ursine RPMs") — packages not being part of a module. In Fedora, these are coming from the Everything repository.
Fixed with https://pagure.io/fedora-docs/modularity/c/2f864a361fef7fcac6935aefc6b0a61ac21277a4?branch=master. I kept an occurrence on purpose in upgrade-paths.adoc. So that people could link the word to the meaning if they found it elsewhere.
Metadata Update from @ppisar: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.