On 9/23/21 7:28 AM, Troy Dawson wrote:
That looks great, and very close to what I've done. I have a couple of variations.I think the biggest is that I set a variable called rhel_name and then change %{name} to %{rhel_name}. It looks like you only had two instances of %{name} but I've had a couple with many instances of it, and this makes it easier. The second is that I usually put a link to the upstream spec file, in comments. I use the CentOS Stream git repo, because it's publicly available. This is mainly for me, cuz I never know where to find them.So, this is at the top of my spec files. # This spec file is derived from the RHEL8 spec file. # They should be kept in sync over time.# https://git.centos.org/rpms/libpinyin/blob/c8/f/SPECS/libpinyin.spec <https://git.centos.org/rpms/libpinyin/blob/c8/f/SPECS/libpinyin.spec>%global rhel_name libpinyin %global _debugsource_template %{nil} But, that's just my preferences. I think yours should be fine.
Thanks, good ideas.
I'm thinking we might want to break this out from a question in the FAQ to it's own page.
+1
Troy
-- Orion Poplawski he/him/his - surely the least important thing about me Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion@xxxxxxxx Boulder, CO 80301 https://www.nwra.com/
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ 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
