Re: How to handle dirty tarballs (Was: Enabling uscan to simply remove files from upstream source)

2012-08-24 Thread Vincent Zweije
On Fri, Aug 24, 2012 at 12:42:43PM +0200, Jonas Smedegaard wrote: || On 12-08-24 at 11:31am, Andreas Tille wrote: || > when working on patches for uscan to implement the removal of files I || > stumbled upon one problem: What to do with dirty tarballs (which are || > unpacking all their files

Re: How to handle dirty tarballs (Was: Enabling uscan to simply remove files from upstream source)

2012-08-24 Thread Jonas Smedegaard
On 12-08-24 at 11:31am, Andreas Tille wrote: > when working on patches for uscan to implement the removal of files I > stumbled upon one problem: What to do with dirty tarballs (which are > unpacking all their files straight to the unpack directory and do not > create a subdirectory). When I wr

Re: How to handle dirty tarballs (Was: Enabling uscan to simply remove files from upstream source)

2012-08-24 Thread Henrique de Moraes Holschuh
On Fri, 24 Aug 2012, Andreas Tille wrote: > do not create a subdirectory). When I write get-orig-source tarballs > I always create a - directory and unpack the content > to this. Should this be implemented as well or do you think it is > better to change as less as possible? You can always creat

How to handle dirty tarballs (Was: Enabling uscan to simply remove files from upstream source)

2012-08-24 Thread Andreas Tille
Hi, when working on patches for uscan to implement the removal of files I stumbled upon one problem: What to do with dirty tarballs (which are unpacking all their files straight to the unpack directory and do not create a subdirectory). When I write get-orig-source tarballs I always create a - d