On Tue, Nov 04, 2025 at 01:46:32PM +0100, Michael J Gruber wrote: > Zbigniew Jędrzejewski-Szmek venit, vidit, dixit 2025-11-04 13:34:02: > > This requires twiddling with the spec when switching between release and > > snapshot builds
> OTOH: If "you" (a maintainer) do not even notice a top-level directory > change then which changes in a tarball do you notice at all? The top-level directory changes depending on how the tarball was created. A very common case is the difference between tarballs for tags and commit hashes autogenerated by github and other forges. > Switching beteen release and snapshot typically requires more than just > a toplevel change, so this could be covered by existing ifdefery. If you look at the commit that I linked, the existing ifdeferry was rather complicated and still didn't cover all of the cases correctly. "Could" does not mean "should". > I don't understand the CI part - is your CI not using the built rpm for > which the tarball doesn't matter? Or automatic spec rebuilds? rpkg from > git source to the rescue ;-) (This particular) CI is building rpms from upstream checkout, but using the distro spec files (currently for fedora, centos, opensuse, debian, ubuntu, and arch). Some support for this is needed in the spec files, but of course we want to make it as lightweight as possible. Zbyszek -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
