Hi all,
Can someone point me to a good resource on how (if permitted) I can make appropriate compat(?) packages to allow for two major versions of the same package to be available? Is this allowed for EPEL?
Thanks
On Mon, Sep 5, 2022 at 2:22 PM Mark E. Fuller fuller@fedoraproject.org wrote:
Hi all,
Can someone point me to a good resource on how (if permitted) I can make appropriate compat(?) packages to allow for two major versions of the same package to be available?
It works pretty much the same way as in Fedora. You can see if a -compat works or if it's a major version (library or otherwise) append the major version/soname to the package name. For instance, EL 7 had CMake 2.8 but there was a demand for version 3 so a cmake3 package was created.
Thanks, Richard
On Monday, September 5, 2022 Mark E. Fuller wrote:
Can someone point me to a good resource on how (if permitted) I can make appropriate compat(?) packages to allow for two major versions of the same package to be available? Is this allowed for EPEL?
You can package compat packages as long as they don't conflict with anything in RHEL. EPEL packages may conflict with other EPEL packages, however.
On Mon, Sep 5, 2022 at 2:22 PM Mark E. Fuller fuller@fedoraproject.org wrote:
Hi all,
Can someone point me to a good resource on how (if permitted) I can make appropriate compat(?) packages to allow for two major versions of the same package to be available? Is this allowed for EPEL?
Thanks
-- Mark E. Fuller, Ph.D. fuller@fedoraproject.org fuller@mefuller.dev @fuller:fedora.im @fuller:one.ems.host https://www.stossrohr.net PGP Fingerprint: 73F1 A30C BDF4 DB4B C75F FD0F D599 E76C FFCA BF60 _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
For naming of the package, please follow the Fedora guidelines for "Multiple packages with the same base name". You'll find many other styles of naming these kind of packages, both in RHEL and EPEL, but please stick with the current Fedora guidelines on this.
https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/#multiple
Also make sure your package name and none of the files in your package conflict with anything shipped in RHEL. This may require manually renaming some files.
https://docs.fedoraproject.org/en-US/epel/epel-policy/#package_maintenance_a...
Once you have a working spec file, you can request a dist-git repo with the exception flag because it would fall under the second bullet point for exceptions.
https://docs.fedoraproject.org/en-US/packaging-guidelines/ReviewGuidelines/#...
If the package is intended to be EPEL-only, make sure to retire the rawhide branch.