Jeffrey Walton wrote: >> More generally, koji shows the build parameters used, which >> include: >> >> Src: git+https://src.fedoraproject.org/rpms/wcm.git#2a4fa39f933f274689c07632e50c7db042247f08 >> >> The commit id can be confirmed as the tip of the f39 branch. >> That's helpful to know whether someone has already committed >> further changes or not. > > Thanks Todd. I never would have figured that out. > > It is too bad the package source files are not under version control. > Lack of version control makes generating diffs for patches a pain in > the butt. The exploded source isn't in git, but Fedora tracks the upstream tarball so patches are made against the source which you get as a result of `fedpkg prep`. There are a couple of patches already in git. Those are tracked directly in git. The source tarballs are kept in a "lookaside" cache and then the sources file records the sha512sum of them. Altogether, all the code which is necessary to reproduce Fedora sources are tracked in git and the lookaside cache. To make a new patch you can either work from the upstream source control or use `git init` in the expanded source tree from `fedpkg prep` and then export it via `git format-patch` and add it to the spec file. You can create the patch via diff (or the gendiff helper script from rpm-build) too. I just use git out of habit. Hopefully some of that is useful and isn't telling you too much of what you already know. :) -- Todd
Attachment:
signature.asc
Description: PGP signature
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
