Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the git-buildpackage package:
> 
> #471581: git-buildpackage --export-export should include the changes in the 
> index
> 
> It has been closed by Guido Günther <[EMAIL PROTECTED]>.
> 
...
> 
>> when I run git-buildpackage --git-export-dir=../build-area/
>> I expect git-buildpackge to export the source tree to the build-area and
>> run the clean command in the exported directory.
>> Atm this isn't the case, it runs clean in the working copy and then does
>> the export.


Hi Guido,

just wondering why you merged 471581 471586?

> This is quiet on purpose since we want to make sure the working copy is
> clean - the export will be anyways (or once we export the index or the
> full wc doesn't have to be).

For the background: I've been using svn-buildpackage with the
--svn-dont-clean option for a few of my packages, where I had to patch
the build system (my preference is to patch Makefile.amS directly and
run autoreconf during build time). In this case I have to clean up the
(re)generated build files, so they don't end up in the diff.gz.
This is admittedly a special case, so my bug report title was badly
worded. A wishlist bug for a --git-dont-clean option would have been
more apt.
I just found out, that I can use --git-cleaner=true, which does exactly
what I want. Would you consider adding this as "tip" to the gbp docs for
svn-buildpackage converts like me?

Cheers,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to