#1273 document Naming Guidelines exception for GStreamer plugins
Closed: fixed a year ago by decathorpe. Opened a year ago by decathorpe.

It looks like packages for GStreamer plugins in Fedora consistently use gstreamer1-plugin-{name} or gstreamer1-plugins-{collection} even though the upstream projects use gst-plugin(s)-{name}, but this is not documented anywhere. It should probably be added here:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#_addon_packages

c.f. https://bugzilla.redhat.com/show_bug.cgi?id=2179161


Why do you say that it needs an "exception"? The naming guidelines (https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#_addon_packages) already say:

If a package is considered an "addon" package that enhances or adds functionality to an existing Fedora package without being useful on its own, its name SHOULD reflect this fact.

The new package ("child") SHOULD prepend the "parent" package in its name, in the format: %{parent}-%{child}.

In this case, the parent package is gstreamer1 so the addon package following the {parent}-%{child} pattern would result in gstreamer1-%{child}.

It might be nice to list it as an example, but why do you say that it needs an exception? I'm probably missing something :)

Well ... at least in this case it conflicts with the guidelines for Rust packages (main package name = crate name) and it would still be good to add it to the list of naming guidelines exceptions for completeness.

There was a PR to add a few clarifications to the Addon naming guidelines (including GStreamer plugins): https://pagure.io/packaging-committee/pull-request/1274

I consider this fixed. Thanks everybody :)

Metadata Update from @decathorpe:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

a year ago

Log in to comment on this ticket.

Metadata
Related Pull Requests
  • #1274 Merged a year ago