Cyril Brulebois wrote: > as you probably know, git is a content tracker, and (at the moment at > least) it completely ignores empty directories. Unfortunately, some > upstream tend to ship tarballs containing empty directories, which lead > to such problems while trying to re-use the delta generated using a git > working copy: > > | tar: graphviz-2.16.1/windows/cmd/bin: Cannot stat: No such file or directory
I've been considering adding support to pristine-tar for checking deltas in and out of git directly. This provides a nice simple interface, and a uniform location for where to keep the deltas. Interface would be something like this: pristine-tar commit ../foo_1.0.orig.tar.gz tags/1.0 pristine-tar checkout ../foo_1.0.orig.tar.gz This also nicely offers a solution to the bug about the empty directories, as well as some other related problems with keeping stuff in git (ie, certian file permissions, owners, and special files that it doesn't preserve either). In the above example, pristine-tar commit can use git-archive tags/1.0 to generate a tarball, and it can then generate a delta that is a delta between that tarball and the .orig.tar.gz. Then pristine-tar checkout reverses the process. Any empty directories, special files, or whatever will be included in the delta. -- see shy jo
signature.asc
Description: Digital signature