On 10/21/2014 06:18 AM, Charles Plessy wrote: > I you generate a orig.tar.xz by yourself, then you can (or have to if it is > the > packaging team's requirement) register it with the command “pristine-tar > <path-to-the-tarball> <git-tag>”. Since it is not much work, I thing that it > is fair to ask people to do it even if personally they do not use it.
If we use xz compression, it simply wont work. And in such case, just using "git archive" achieves the same goal, but with a single unique packaging branch, which is a way better. The only thing is that this should be wired-in in debian/rules (which is what I always do). > Pristine-tar is much about preparing a package update while not having access > to the Debian archive at the same time. Doing this with a stored git tag and "git archive" provides the same convenience. > Two' invokations of git-archive will > not necessary generate byte-identical tarballs. Same with pristine-tar if using xz... And there's also this: On 10/21/2014 11:15 AM, Matthias Urlichs wrote: > Two invocations of pristine-tar will not, either, if you happen to > use a different version of tar than the one used to prepare the > pristine-tar entry. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5445e154.9050...@debian.org
