Re: gauche releases

Shiro Kawai <[email protected]> writes:

> Debian's tool needs a page that lists links to tarballs?  I can add that
> feature to the web api.

uh - I really don't want to "waste" your time, but yes

> Does it need to find signature files as well?

as far as i understand, it wouldn't hurt, but it looks like uscan has
different modes to derive the signature url from the tarball url. So I
think it would be more important that if the tarball url is
https://practical-scheme.net/vault/Gauche-0.9.16.tgz
that the signature is available at url + ".asc":
https://practical-scheme.net/vault/Gauche-0.9.16.tgz.asc

> The advantage of using web api is that I can filter out unnecessary files.
> For example, in general, you don't want to treat "snapshot" releases as
> upstream updates; they may not be as stable as real releases.   0.9.15-p2
> is the exception, and I can include them as I wish.   And of course you
> don't want to include bleeding-edge tarballs, as they may even be broken.

if you really want to do this, it would be great and afterwards you
would have control over what debian (and maybe other distros?) would
consider a new upstream release. (note: you don't have to worry too much
about breaking things as there is still manual review/testing)

But if you want to safe time/work we could also agree on the url regexp
to match the releases to consider automatically. At the moment this
would be:

https://practical-scheme.net/vault/Gauche-(\d[\d\.]*)\.tgz

=> snapshots wouldn't be considered

Best regards
Jens