On Wednesday, 14 August 2024 16:43:54 CDT Agathe Porte wrote: > Or maybe I could tar the upstream .git folder and store everything else > as plain files? But still a binary blob in source package. And > extracting the tar into a .git in the filesystem in /usr/share/ may > raise a lot of Lintian warnings? Perhaps you could include the contents of the git repo in the source package, then in d/rules run something like `cd usr/src/qmk_firmware && git init && cp files . && git add -A && git commit`. That way, you just have regular files in the source package, but you generate a synthetic Git repo in the build process. Reproducibility might be difficult, given that git uses the current date and such for creating commits. Doesn't sound insurmountable though! -- Piper McCorkle (~pmc) contact@piperswe.me https://piperswe.me/ PGP fingerprint: 47EA 31C6 C718 6273 1A21 81F8 BDD8 9B35 FBA0 CD06
Attachment:
signature.asc
Description: This is a digitally signed message part.