My use case of git-buildpackage
Guido Günther
agx at sigxcpu.org
Thu Nov 24 17:47:07 UTC 2011
On Thu, Nov 24, 2011 at 06:21:07PM +0100, Daniel Dehennin wrote:
> Yaroslav Halchenko <debian at onerussian.com> writes:
>
> > On Thu, 03 Nov 2011, Daniel Dehennin wrote:
> >> First, I'm not a Debian maintainer, I mostly do some package for my
> >> personal use, to follow SVN trunk or git HEAD of some softwares.
> >
> > that is the idea behind Debian -- personal use could benefit others
> > alike -- why not to share those packages with the rest of debian
> > community through finalizing packaging so it is compliant with debian
> > standards, and then seeking sponsored upload?
>
> There is already a debian package for the 2 or 3 packages I build, my
> work is no more than something like:
>
> git clone git://upstream.software/project && cd project
> git remote add debian git://git.debian.org/project
> git fetch debian
> git checkout -b snapshot
> git merge debian master
> git buildpackage
>
> Another point is that I'm working in a french educational ubuntu
> derivative and try to do things not to badly ;-)
>
> >> There are some items about which I would like to discuss, like:
> >> - automatic handling of debia/changelog
> >
> > git-dch?
>
> Yes, I'm looking at a good workflow to use it without storing it in my
> branches, this will permit to avoid conflicts during merge/rebase.
>
> When I'll merge a temporary branch of my doc, I'll explain a workflow
> with tags, git rev-log, git describe.
>
> >> - multi-distributions/version packaging (and avoiding conflicts)
> >
> > for neurodebian we use our backport-dsc
> > http://github.com/neurodebian/neurodebian/blob/HEAD/tools/backport-dsc
> >
> > NB yet to create a blog post on our set of little helpers, altogether
> > usually we just call nd_build4all X.dsc to get it built across releases
> > of debian and ubuntu... interested to learn more?
>
> Yes, of course, I'm looking at validation of packages, with piupart, CD
> building and automatic installation tests.
>
> >> - management of orig.tar.gz
> >
> > do you mean "filtering"? git-import-orig does that if you specify
> > 'filter' option in your debian/gbp.conf for the package
>
> Every example I saw use git-import-orig, what about using upstream VCS
> directly and not the tar.gz?
You can merge the upstream branch on your debian branch, create the orig
tarball using git-buildpackage and use pristine-tar to store the binary
delta in the repo. I plan to add an extra command for this in
git-buildpackage in the future.
Cheers,
-- Guido
More information about the vcs-pkg-discuss
mailing list