support/download: reproducible archives whatever tar version (branch yem/dl-git-tar-pax-2)
Get series with b4
b4 am 20201229142547.GO1680670@scaerVersions newest first · linked by author and title
- v3 Latest posting 3/30 of 10 patches 0 repliesNew
- v3 posting 2/30 of 10 patches 0 repliesSuperseded
- v3 posting 1/310 patches 0 repliesSuperseded
Earlier versions · 2
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v2 | 9 patches | 0 replies | Superseded | |
| v1 | 0 of 7 patches | 0 replies | Superseded |
Patches in v3 posting 3/3 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)
Thomas, All,
On 2020-12-29 15:15 +0100, Thomas Petazzoni spake thusly:
Quoted 17 lines
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 6 lines
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.
Fortunately, we do not yet have as many cargo (0) or go (8) packages as we have git-based downloads... ;-)
Quoted 2 lines
We also end up with pretty weird tarball names, like _cargo_br1.tar.gz.
Well, this would be for a git-based download. A wget-based download would get foo-1.2_cargo.tar.gz...
Quoted 1 line
But oh well, perhaps that the price to pay to get all of this to work ?
Yes, I don't mind much about that naming. I just think we should make it simple to write packages and hashes, with simple rules.
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'