fesco

#3000 Recommended way to follow new upstream releases in EPEL
Closed: Invalid by mlichvar. Opened by mlichvar.

Closed: Invalid
Reopen Issue

I'm trying to get the latest gpsd version to EPEL8/9. There are already older versions available and they provide a library with a different API/ABI, so according to the policy I need to submit a new package.

The users that are asking for this will likely need even newer versions as they will be released. To avoid adding more packages I though it would be best to add it as a -latest package which will not have any development files, so no ABI/API can be broken, and it can be expected to be rebased freely.

Review request: https://bugzilla.redhat.com/show_bug.cgi?id=2196598

Does that seem reasonable to you? In EPEL I see many packages with versions in their names, but I see only two -latest packages: java-latest and xe-guest-utilities-latest, so I'm not sure if this is a recommended practice.

Have you seen the Fedora guidelines on the topic?

That one suggests a -stable suffix. I see only one package in EPEL using that: rust-stable. Would that be preferred over -latest?

Edit: actually, the full name of the package is rust-stable_deref_trait, so that might not be a good example.
Edited by mlichvar

This might be worth moving to the epel steering comittee folks?

https://pagure.io/epel / epel-devel@lists.fedoraproject.org

Ok, moved to https://pagure.io/epel/issue/228

Metadata Update from @mlichvar:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.