support/download: reproducible archives whatever tar version (branch yem/dl-git-tar-pax-2)
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest posting 2/20 of 10 patches 0 repliesNew
- v3 posting 1/20 of 10 patches 0 repliesSuperseded
- v10 of 7 patches 0 repliesSuperseded
Patches in v3 posting 2/2 No applies recorded yet
None of the 10 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [Buildroot] [PATCH 00/10 v3] support/download: reproducible archives whatever tar version (branch yem/dl-git-tar-pax-2)
Quoted 14 lines · On Tue, 29 Dec 2020 14:46:10 +0100 "Yann E. MORIN" <[email protected]>…
I was also considering a similar mechanism for the vendoring thingy...
My initial thought was to have a ways to extend this extra format version. I am not entirely sure how to do it, but probably something along the lines of:
define cargo-inner $(2)_VENDOR_VERSION = _cargo endef define generic-inner $(2)_SOURCE_EXT = $$($(2)_VENDOR_VERSION)$$(BR_FMT_VERSION_$$($(2)_SITE_METHOD)).tar.gz endef
Quoted 2 lines
But this is not as nice as I'd like it to be... If you have another idea, please be my guest. ;-)
Hum, yes, that's an idea. We would still to change in lock-step all .hash files for all cargo/go packages, even the ones that don't need any vendoring. We also end up with pretty weird tarball names, like _cargo_br1.tar.gz.
But oh well, perhaps that the price to pay to get all of this to work ?
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com