On Sun, Nov 04, 2007 at 03:37:28PM +0100, Guido Guenther wrote: > Hi Mike, > On Fri, Nov 02, 2007 at 09:46:48PM +0100, Mike Hommey wrote: > > Well, everything is in the subject. One of the culprits is copy_from(), > > which reads/writes the whole tree one while it is far from necessary. > What would you recommend? Using hardlinks? We can't untar right into the > git repo since we might need to mangle/filter files. Any suggestions are > very welcome.
Why do you need to mangle/filter files ? > > Another one is the fact that import-dsc also runs dpkg-source -x, which > > means the .orig.tar.gz gets uncompressed and written out twice. > What should we do about this? Not using "dpkg-source -x" would mean > getting into the "details" of how debian patches are being applied - > that's easy enough at the moment since we only have a single diff.gz but > we'd have to keep up with changes in the packaging format ourselves > then or am I missing something? We won't get a different source format before some time, so in the meanwhile, options can surely be added to dpkg-source... but even so, IIRC the new source format allows to have several orig tarballs, which would require special care from git-buildpackage... so you'll need to get into the details anyway. > > Another one is the fact that when importing for the first time, git-commit, > > called without -q, generates a very long diff summary (since one end of > > the diff is void) for no real use. > I tried this and git-buildpackage now ommits the output but the speedup > is quiet small - unfortunately. On big trees, it saves a few seconds. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
