On Sat, Feb 05, 2011 at 04:31:54AM +0000, Miguel Colon wrote:
Joel, it seems that you have to live with manually popping the patches from the stack, until the integration matures.Kind of late but what I do is add among other things: [git-buildpackage] export-dir = ~/git-repo/multimedia/output to the ~/gbf.conf file. This would just make a temporary copy of the source in that directory / compile it (with pbuilder in my case) / remove the temporary source if there was no error (with error the source is left there so you could analyze it if needed) and stores the resulting package files there. It leaves the original source untouched so he can run git-buildpackage as many times as he wants in a row which was his original goal. This method does not require adding the local-options file and is useful if you want to avoid adding that file to multiple git trees.
Yes, this is another style of dealing with the marriage of dpkg-source and git-buildpackage: let git-buildpackage "hide its existense" by exporting to a non-VCS dir before handing over to dpkg-source.
I prefer prefer a closer marriage. Also because that helps discover packaging flaws regarding not claning up properly in the clean target.
If for some reason he want to trash the original source (like using dpkg-buildpackage) he could add an alias to ~/gitconfig [alias] undo = !git reset --hard && git clean -xdfand do "git undo" but this command should be used with care to say the least.
I find it dangerous to throw brutal suggestions like that without further elaborating what it does.
- Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Description: Digital signature
_______________________________________________ pkg-multimedia-maintainers mailing list firstname.lastname@example.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers