Guido Guenther wrote:
> Hi David,
> On Fri, Feb 16, 2007 at 10:24:54PM -0500, David Nusinow wrote:
>
>> I'd like to make use of pre-existing .orig.tar.gz's. I have a large
>> of these lying around for more stable parts of xorg, and I'd like to just
>> have git-buildpackage use them rather than import them in to the
>> repository. I think this is the last issue that's keeping me from using
>>
> So you only want to maintain debian/ in the git-repository? This is
> certainly doable but git is so space efficient (git-repack -a,
> git-prune-packed) that you won't gain much by this - are there other
> reasons for keeping the upstream sources out of the archive?
> Cheers,
>
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
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.
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?
Brice
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
