Bug#763071: devscripts: [uscan] allow setting download compression ordering (prefer xz over gz)

[Andreas Metzler]

On 2014-09-29 James McCoy <jamessan at debian.org> wrote:
> On Sat, Sep 27, 2014 at 06:50:06PM +0200, Andreas Metzler wrote:
[...]
>> ... uscan finds both .gz and .xz but selects the gzip version for
>> download. Switching the two alternatives in the regex does not change
>> this.

[...]
> The ordering actually comes from the ftp listing.  That being said, why
> not just remove the bz2/gz parts of the regex if you know upstream is
> shipping xz?  I don't see the benefit of matching the other extensions
> (especially the bz2), when you know upstream already provides the
> extension you want.

Hello,

two reasons:
a) Robustness. I still want uscan (PTS) to find new versions if
upstream suddenly decides to switch encryption schemes (gz for
compatibilty + whatever is the enhanced encryption scheme of the
month.)

b) Usually I come from a different direction: Upstream currently only
provides .gz, but I want automatically use .bz2 or .xz when they
enhance their service.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'