Thomas Koch wrote: > I'd prefer not to have an isolated branch for the pristine-tar data but to > have a folder in debian/ e.g. debian/pristine-orig/ to hold the data of > pristine-tar. > > First it happens often that people make mistakes when committing a tarball > with pristine-tar. It's hard for git novices to reset the pristine-tar branch > to undo the commit. It's much easier to delete a delta file from the > filesystem instead of commiting it. > > Second it seems to be the right thing to have everything in one branch. > > - - If I tag my debian release with a signed git tag I sign just the master > branch. An attacker could still try to manipulate the pristine-tar branch. > > - - It might be possible that the pristine-tar branch gets lost or isn't up to > date with the version referenced in the changelog in the master branch.
It seems that this would need dpkg-buildpackage toolchain changes, otherwise the pristine-tar data would be included inside the source package, which is not desirable. You can of course use pristine-tar without commit and put the delta created by gendelta wherever you want. -- see shy jo
signature.asc
Description: Digital signature
