After beating git-debimport into submission for some time, I now have a reasonably coherent git archive of tcpdump with proper commit dates, correct attribution and a tag layout compatible with what git-buildpackage does.
Along the way I tried out guilt (git + quilt). Unfortunately, my trust level almost immediately reached zero.
Apart from that, today pretty much sucked. Prepare your sleep apparatus. Better luck tomorrow.
04 October 2007
Balance is but a shimmering notion
Subscribe to:
Post Comments (Atom)
3 comments:
Interesting, I had not heard about the gitpkg package before. I've been using git-buildpackage so far.
Being able to use the --git-tag option, importing an initial dsc file, and adding upstream releases is easy with git-buildpackage. Alas, it does not do a good job with importing multiple dsc files, in order to build a history. Additionally, its documentation is not always clear about where you are supposed to be in the directory tree when calling a specific script: git-buildpackage and git-import-orig are called from the working directory, while git-import-dsc is called from the directory above where the git repo exists. The git repo created by git-import-dsc is placed into a directory named exactly after the package, and if that directory exists aleady, it chokes.
From an initial look, it seems like git-debimport provides a great replacement for git-import-dsc -- it'd be nice to see it bundled with git-buildpackage.
Yeah, I used gitpkg's git-debimport only to create the initial repo, I plan to use git-buildpackage from there on. See this thread for more on gitpkg vs. git-buildpackage.
You can specify the tag format the git-buildpackage, etc tools expect using
{upstream,debian}-tag
so no need to move tags into a format the tools expect, just tell the tools what you want.
Post a Comment