Bug#809806: uscan: Writes .uscan.log file unconditionally

[Osamu Aoki]

OK.  I unmerged and keep this bug separate.

On Sun, Jan 31, 2016 at 08:04:22AM -0400, David Prévot wrote:
> Hi Osamu et al.,
> 
> Le 31/01/2016 03:42, Osamu Aoki a écrit :
> > On Mon, Jan 04, 2016 at 11:08:40AM +0100, Joachim Breitner wrote:
> >> Package: devscripts
> >> Version: 2.15.10
> 
> 
> >> I believe that uscan should either write this log file (what is it for
> >> anyways?) to the destdir as well, or provide a way to disable writing
> >> it.

This is used to check if upstream tarball is changed or not.

Even *tar..gz -> *.tar.gz repacking may result in different file.
Also automatic file removal is another cause for differences which needs
checking. This is used to check such thing happend or not.

> > Do you really insist to have an option to disable this log?  If not,
> > let's go with this pending fix for Bug #809662.
> 
> Pretty please yes, and extra points if that option becomes the default
> behavior (i.e., the conservative way, don’t let uscan write a log file
> unless explicitly asked to). Having a bunch of almost empty useless
> files in my development directory is not something I’m expecting.
> 
> $ cat ../*uscan.log
> # uscan log
> # uscan log
> # uscan log
> # uscan log
> # uscan log
> […]

OK.  I see your point.  Let me think.