On Wed, 2021-11-10 at 13:10 -0600, Jason L Tibbitts III wrote: > > > > > > Troy Dawson <tdawson@xxxxxxxxxx> writes: > > > If I remember right, the spec file name needs to be in the format > > <dist-git-repo-name>.spec Thus, the spec file needs to be > > openssl3.spec, and thus you aren't really renaming it. :) > > Yes, assuming that EPEL doesn't deviate: > > https://docs.fedoraproject.org/en-US/packaging-guidelines/#_spec_file_naming > > I believe various tools will make the assumption that the specfile is > named accordingly. > Yeah, let's avoid that minefield then. Mock seems happy with it but I'm not sure other tools will be. Per the EPEL meeting, we're going with Neal's idea of basing this on the C9S spec rather than Rawhide; the intent will be to maintain this as an `openssl3` dist-git repo in Fedora but populate it with what I'm developing in https://gitlab.com/michel-slm/openssl3/-/commits/epel8 - so we can easily merge changes from C9S (which should be less of a moving target than Rawhide). Given openssl3 is not in Fedora <= 35 it might be worth having this in Fedora 35 and below too, but let's start with EPEL This shows the minimum changes needed to: - have openssl3-libs parallel installable with openssl-libs (tested in mock for x86_64) - mark the base, devel, and perl subpackages as conflicting - openssl3 and openssl both ship binaries in %{_bindir} - ditto with openssl3-perl and openssl-perl - openssl3-devel and openssl-devel both ship headers and includes with the same names I had to exclude two config files in openssl3-libs that are also in openssl-libs; hopefully the old configs work with the new packages but I don't have an immediate test case. If this looks sane to people, I can open a review request. Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/michel@xxxxxxxxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure