Goswin von Brederlow wrote: > I think hg can be done the same way git is done. > > Create a pristine-tar branch and store package_version.orig.tar.gz.delta > and package_version.orig.tar.gz.id files there. > > For checkout "git show" becomes "hg cat -r pristine-tar <file>". > > For commit there is some BIG MAGIC being done for git to sneek in the > new files without disrupting the working dir. No idea what the > respective mercurial procedure would look like. Manually I would > switch branches, generate the files, add them, commit and switch back.
Right, but pristine-tar can't get in the user's way by doing things to their working copy. It could even be unclean, or have some other VCS activity going on at the same time. > Maybe the best thing would be to clone the repository to a tempdir, > add the files there and push them back. Have to try that. Yes, that's the safe, slow, way to do it. For svn, that's probably the only way, short of linking to svn protocol libraries, which is why I haven't tried to support svn. I imaging hg can clone faster and w/o hitting the net though. -- see shy jo
signature.asc
Description: Digital signature