Bug#738977: uscan: howto download from alioth ...

[Osamu Aoki]

Hi,

On Tue, Sep 22, 2015 at 07:00:05PM -0400, James McCoy wrote:
> On Wed, Sep 23, 2015 at 02:32:03AM +0900, Osamu Aoki wrote:
> > After having a locally functioning multi-upstream tarball support for
> > uscan, I realize this multiple download capability can be extended to
> > address downloading sig file too.
> > 
> > opts="sigmode=next" <URL> <pattern for tarfile> debian
> > opts="sigmode=prev" <URL> <pattern for sigfile> prev uupdate
> > 
> > <version> is prev which mean to match the previous download version.
> > 
> > If we use matching pattern for 3989, 3990, ... in the path within href
> > as non-capturing (?:\d+?), the changing number does not impact the
> > download.  Downloading version match is done exactly equal to the
> > previously download one.
> 
> With this proposed functionality, if the sigfile was earlier on the page
> then the watch file would have to be written as below?
> 
>   opts="sigmode=next" <URL> <pattern for sigfile> prev uupdate
>   opts="sigmode=prev" <URL> <pattern for tarfile> debian

This is watch file.
 
> Having to rely on the order of the links in the page seems fragile.

Hmmmm... I think I did not explain enough.  Your concern was my concern.

There is no addition involved which original bug report requested.

> It may make more sense to push the knowledge that we're looking for a
> sigfile into the code that searches for tarfile.

I do not understand what exactly you mean....

Basically, sigfile needs to be searched like what exactly we do to
search http;://URL page looking for tarfile with the match pattern for
fixed version request. 
 --download-version
 --download-current-version
prev/next are there just to indicate passing version for match.

> Then we collect links that match the pgpsigurlmangle while we're
> collecting the links for tarfile and figure out which are the correct
> links after the fact, like we already do for tarfile.

Maybe I should show what I have here as a branch to the master.  Then it
should be clear.

I need to proof manpage and improve logging capabilty for multiple
upstream tarball packaging ... but key functions are there.

Look for multitar branch :-)

Thanks,

Osamu