Bug#820494: origtargz: leaves "upstream" files in "master" after invocation

[Dmitry Smirnov]

On Saturday, 9 April 2016 1:06:03 PM AEST Christoph Berg wrote:
> Right, but this is exactly what's documented, and what origtargz is
> supposed to be doing - give you a full working tree to work on.

Fair enough. :)

I just want to note that phrase "optionally unpacks it into the current 
directory" in manual page suggests that unpacking should not be done by 
default. Nor the name of the utility implies that unpacking is its purpose 
(and not the unwanted side effect) of this utility.


> Using origtargz to simply generate (fetch, copy, ...) the tarball to
> .. is a legitimate use case, but you'll need to pass --unpack=no to
> disable the automation on "almost empty" directories.

OK.

> I'll also update the manpage to make the --unpack=once behavior more clear.

Thanks.

-- 
Cheers,
 Dmitry Smirnov.

---

In questions of science, the authority of a thousand is not worth the
humble reasoning of a single individual.
        -- Galileo Galilei
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/devscripts-devel/attachments/20160409/9c523938/attachment.sig>