Dear Guido,

If I am not wrong, gbp doesn't have a simple method to just export the
source tree (upstream orig + debian/), without building the packcage.

It would be nice to have something like:

    gbp export-source-tree DIR

The simplest hack that I've found is (thanks folks in #debian-devel)
somthing like this:

gbp buildpackage \
    --git-ignore-branch \
    --git-ignore-new \
    --git-export-dir=${SOURCE_DIR} \
    --git-no-purge \
    --git-builder="dpkg-buildpackage" \
    -S -d -nc -us -uc

but it needs to build the source package.

Could you please consider this new feature?

Cheers,

Hi,

As noted on irc you can just use `/bin/true/` as builder:

    gbp buildpackage --git-export-dir=/tmp/foo --git-builder=/bin/true --git-no-pbuilder --git-no-hooks

but if somebody comes up with a patch that moves that common code into a
`export_source` command (including manpage) that would be nice too.
Cheers,
 -- Guido

El 09/09/20 a las 11:11, Guido Günther escribió:

For completeness:

     gbp buildpackage --git-export-dir=/tmp/foo --git-builder=/bin/true --git-no-pbuilder --git-no-hooks --git-no-purge

Thanks! I've already tried `--git-builder=/bin/true`, but I was missing
`--git-no-pbuilder --git-no-hooks`.

ACK. Sadly I don't have currently enough free cycles, so I cannot
promise I'll be able to do it myself.

Thanks,

Hi,

Same here but maybe this helps a little

https://git.sigxcpu.org/cgit/git-buildpackage/commit/?id=c02938fd87042429d6d6102ba55e2b7eee9712f8

Cheers,
 -- Guido

El 09/09/20 a las 13:25, Guido Günther escribió:
...

Great, thanks!

Forgot to say that would be also useful to have an argument to name the
directory where the debianized source would be extracted, other than
package-name-version.

Cheers,

私に戻ってください。
Please get back to me.