[git-buildpackage] Would it be possible for pristine-tar to not be an absolute path?
Nish Aravamudan
nish.aravamudan at canonical.com
Sun Jan 7 20:31:07 CET 2018
On Jan 7, 2018 11:09, "Guido Günther" <agx at sigxcpu.org> wrote:
Hi,
On Fri, Jan 05, 2018 at 09:55:30PM -0800, Nish Aravamudan wrote:
> Hi Guido,
>
> On Wed, Aug 30, 2017 at 12:47 PM, Guido Günther <agx at sigxcpu.org> wrote:
>
> <snip>
>
> >> To be clear, we only use gbp for orig tarball handling currently (we
> >> import-orig the tarballs published for Debian & Ubuntu, and use
> >> buildpackage (eventually export-orig, once it's available) to get the
> >> tarballs back out).
> >
> > gbp export-orig is already in the versions in experimental. It will gain
> > some more features in the near future (like checking out arbitrary
> > versions without having a working copy).
>
> Have the parenthetical changes landed yet? Or does both
> gbp-buildpackage (when using pristine-tar, or not) and gbp-export-orig
> only extract tarballs for HEAD?
gbp-buildpackge extracts tarballs for the version you're building (I
think that's the only thing that makes sense).
Yeah, that makes sense.
gbp export-orig should
support exporting any version given a debian revision:
gbp export-orig 10.0.1-1
We could assume '-1' if not given:
gbp export-orig 10.0.1
I should be a simple as fetching the right DebianSource in main() but I
did not get around to look into that.
Hrm,
https://honk.sigxcpu.org/projects/git-buildpackage/manual-html/man.gbp.export.orig.html
and the --help don't suggest a version parameter? If it works, though, I
will use it!
Thanks,
Nish
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sigxcpu.org/pipermail/git-buildpackage/attachments/20180107/00346d79/attachment.html>
More information about the git-buildpackage
mailing list