Hi, On Sat, Jun 04, 2016 at 11:24:20AM +0200, Guido Günther wrote: > Hi, > > On Thu, Dec 30, 2010 at 05:24:02PM +0100, Guido Günther wrote: > > this makes it possible for third party tools git-buildpackage to verify > > that the checked out tarball is the one expected. > > Any chance we can get this feature. This would allow us to easily catch > cases where people have broken tarballs from somewhere (and gbp would > therefore not regenerate them because they have the corret name). It > would also help us to detect compressor changes.
I'm not sure letting other tools poke at the pristine-tar implementation details is a good idea. Also, I agree with Joey's assessment earlier that this should be in the delta file itself. We could perhaps have a new command that takes a tarball and tests whether it matches the corresponding checksum, stored in the pristine-tar delta file; or even better, we could make `pristine-tar checkout` do nothing if the output filename already exists and matches the checksum. That would satisfy your use case, I guess? -- Antonio Terceiro <[email protected]>
signature.asc
Description: PGP signature
