Re: gauche releases
Shiro Kawai <[email protected]> Thu, 28 Nov 2024 00:22:38 -1000
| Newsgroups | gmane.lisp.scheme.gauche |
|---|---|
| Message-ID | <CALN0JNHpJaLDpu1GYc-XXf9Jc8pnYCqftqRfv8OB8+U2RJe-Nw@mail.gmail.com> |
--===============0480098031999608817== Content-Type: multipart/alternative; boundary="000000000000d3f3a40627f6761d" --000000000000d3f3a40627f6761d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hm, I see. From the description, `https://practical-scheme.net/vault/` and regexp match seems sufficient for debian. Special-cases like 0.9.15-p2 can also be handled by Debian side. If that's the case, yes, please keep using ` https://practical-scheme.net/vault/`. On Wed, Nov 27, 2024 at 11:45=E2=80=AFPM Jens Thiele <[email protected]> wrote= : > Shiro Kawai <[email protected]> writes: > > > Debian's tool needs a page that lists links to tarballs? I can add tha= t > > 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 broke= n. > > 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 > > =3D> snapshots wouldn't be considered > > Best regards > Jens > > > _______________________________________________ > Gauche-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/gauche-devel > --000000000000d3f3a40627f6761d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hm, I see.=C2=A0 From the description, `<a href=3D"ht= tps://practical-scheme.net/vault/`">https://practical-scheme.net/vault/`</a= > and regexp match seems sufficient for debian.=C2=A0 Special-cases like 0.= 9.15-p2 can also be handled by Debian side.</div><div>If that's the cas= e, yes, please keep using `<a href=3D"https://practical-scheme.net/vault/`"= >https://practical-scheme.net/vault/`</a>.</div><div><br></div><br><div cla= ss=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_at= tr">On Wed, Nov 27, 2024 at 11:45=E2=80=AFPM Jens Thiele <<a href=3D"mai= lto:[email protected]">[email protected]</a>> wrote:<br></div><blockquote clas= s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r= gb(204,204,204);padding-left:1ex">Shiro Kawai <<a href=3D"mailto:shiro.k= [email protected]" target=3D"_blank">[email protected]</a>> writes:<br> <br> > Debian's tool needs a page that lists links to tarballs?=C2=A0 I c= an add that<br> > feature to the web api.<br> <br> uh - I really don't want to "waste" your time, but yes<br> <br> > Does it need to find signature files as well?<br> <br> as far as i understand, it wouldn't hurt, but it looks like uscan has<b= r> different modes to derive the signature url from the tarball url. So I<br> think it would be more important that if the tarball url is<br> <a href=3D"https://practical-scheme.net/vault/Gauche-0.9.16.tgz" rel=3D"nor= eferrer" target=3D"_blank">https://practical-scheme.net/vault/Gauche-0.9.16= .tgz</a><br> that the signature is available at url + ".asc":<br> <a href=3D"https://practical-scheme.net/vault/Gauche-0.9.16.tgz.asc" rel=3D= "noreferrer" target=3D"_blank">https://practical-scheme.net/vault/Gauche-0.= 9.16.tgz.asc</a><br> <br> > The advantage of using web api is that I can filter out unnecessary fi= les.<br> > For example, in general, you don't want to treat "snapshot&qu= ot; releases as<br> > upstream updates; they may not be as stable as real releases.=C2=A0 = =C2=A00.9.15-p2<br> > is the exception, and I can include them as I wish.=C2=A0 =C2=A0And of= course you<br> > don't want to include bleeding-edge tarballs, as they may even be = broken.<br> <br> if you really want to do this, it would be great and afterwards you<br> would have control over what debian (and maybe other distros?) would<br> consider a new upstream release. (note: you don't have to worry too muc= h<br> about breaking things as there is still manual review/testing)<br> <br> But if you want to safe time/work we could also agree on the url regexp<br> to match the releases to consider automatically. At the moment this<br> would be:<br> <br> <a href=3D"https://practical-scheme.net/vault/Gauche-(%5Cd%5B%5Cd%5C.%5D*)%= 5C.tgz" rel=3D"noreferrer" target=3D"_blank">https://practical-scheme.net/v= ault/Gauche-(\d[\d\.]*)\.tgz</a><br> <br> =3D> snapshots wouldn't be considered<br> <br> Best regards<br> Jens<br> <br> <br> _______________________________________________<br> Gauche-devel mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">Gau= [email protected]</a><br> <a href=3D"https://lists.sourceforge.net/lists/listinfo/gauche-devel" rel= =3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/listi= nfo/gauche-devel</a><br> </blockquote></div></div> --000000000000d3f3a40627f6761d-- --===============0480098031999608817== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============0480098031999608817== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gauche-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gauche-devel --===============0480098031999608817==--