Bug#525319: Please add mercurial (hg) support
Package: pristine-tar Version: 0.21 Severity: wishlist Please add mercurial (hg) support to pristine-tar. MfG Goswin -- System Information: Debian Release: squeeze/sid APT prefers unstable-i386 APT policy: (500, 'unstable-i386'), (500, 'experimental-i386'), (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22.2-mrvn Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages pristine-tar depends on: ii libc6 2.9-3 GNU C Library: Shared libraries ii perl-modules 5.10.0-19 Core Perl modules ii xdelta 1.1.3-8 A diff utility which works with bi ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages pristine-tar recommends: ii bzip2 1.0.5-1high-quality block-sorting file co ii pbzip21.0.4-2parallel bzip2 implementation pristine-tar suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525319: Please add mercurial (hg) support
Goswin Brederlow wrote: Please add mercurial (hg) support to pristine-tar. Since this requires a good deep knowledge of each VCS, and I only know two well enough[1] personally, I'd need help to do that. The sort of thing that would be useful is if you can manually generate some pristine-tar deltas, and figure out the best way to store them in a mercurial repo, and send instructions / examples of doing just that, manually, and also of how pristine-tar can extract a delta from the repo later, as well as a good clear explanation of why the way you chose is the Best Way for mercurial. -- see shy jo [1] git and svn, but all my svn knowledge says it will suck to support svn signature.asc Description: Digital signature
Bug#525319: Please add mercurial (hg) support
Joey Hess jo...@debian.org writes: Goswin Brederlow wrote: Please add mercurial (hg) support to pristine-tar. Since this requires a good deep knowledge of each VCS, and I only know two well enough[1] personally, I'd need help to do that. The sort of thing that would be useful is if you can manually generate some pristine-tar deltas, and figure out the best way to store them in a mercurial repo, and send instructions / examples of doing just that, manually, and also of how pristine-tar can extract a delta from the repo later, as well as a good clear explanation of why the way you chose is the Best Way for mercurial. -- see shy jo [1] git and svn, but all my svn knowledge says it will suck to support svn 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. 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. MfG Goswin PS: I've CCed the mercurial maintainer team. Maybe someone there is interested or can help. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525319: Please add mercurial (hg) support
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
