[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How does team maintenace of python module works?

On 20/02/13 14:14, Thomas Goirand wrote:
> Now, do you know if it is possible to use git-buildpackage
> without storing the full upstream source in a branch?

Yes, most conveniently done via 'overlay = True' in debian/gbp.conf. You
have to supply a copy of the upstream tarball as you would for plain
debuild or svn-buildpackage, typically in .. or ../tarballs (also
configurable in gbp.conf).

I do this for openarena-data and its various related packages, because
the full upstream source is *huge* (mostly audio, graphics etc.),
particularly once I included the actual source files, so keeping a copy
in git would be a significant problem; and the upstream source is
unlikely to ever be patched in Debian (not that binary files patch well
anyway), so there's no point.

I don't think debian-directory-only maintenance in git is a good idea
for typical packages containing "mostly" code - you lose the ability to
use gbp-pq to manage patches, for instance. openarena and ioquake3 do
have an 'upstream' branch, using the typical git-buildpackage workflow.


Reply to: