Re: EPEL: packaging multiple versions and compat packages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 5, 2022 at 2:22 PM Mark E. Fuller <fuller@xxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxx
> fuller@xxxxxxxxxxxx
> @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@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxxxxx
> 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_and_update_policy

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/#_package_review_process

If the package is intended to be EPEL-only, make sure to retire the
rawhide branch.

-- 
Carl George
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux