Hi Brice, thanks for the clarification. On Tue, May 22, 2007 at 10:13:06PM +0200, Brice Goglin wrote: > I guess David wanted to try git-buildpackage for X packages and I just > had a look at this too. For clarification, Xorg upstream also uses git, > so we have the upstream code in a branch (upstream-unstable or > upstream-experimental) and upstream+debianpackaging in another branch > (debian-unstable or debian-experimental). And we would basically build > packages for unstable using: > git-buildpackage --git-upstream-branch=upstream-unstable > --git-debian-branch=debian-unstable or specify this in gbp.conf
> However, being able to use the actual tarball that upstream ships might > be good, instead of recreating it from our upstream-unstable branch. So > I second David's request for something like a --git-orig-targz > foo.tar.gz (or bz2) option. Well, git-buildpackage doesn't create a orig.tar.gz at all, if it finds one. Do you want to be able to give a different name that is then copied over to <upstream-version>.orig.tar.gz? > In the end, thinking about all this, I am not sure git-buildpackage is > really useful for X packages since upstream uses git. Why does it buy > us? Avoiding -i.git? * making sure you have everything committed nicely * automatic tags (to your own gusto) after a successful build * automatic push outs to altioth after a successful build+tag * automatic signed tags (via gbp.conf) This might not be of any actual use for xorg packaging though. Cheers, -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
