On Wed, Aug 9, 2017 at 6:54 PM, Shengjing Zhu <i...@zhsj.me> wrote:

> Thanks for the comment.
> On Wed, Aug 9, 2017 at 10:54 PM, Michael Stapelberg
> <stapelb...@debian.org> wrote:
> > 1. I think that infrastructure which the pkg-go team critically and very
> > visibly depends on should eventually be hosted by DSA under debian.org.
> I
> > don’t see them hosting this special “workaround” service, when there
> already
> > is infrastructure in place to run uscan.
> Well it can be hosted by DSA, or even don't use web service. Maybe
> uscan can just call its cli tool.

As much as I’d like to see more Go code within Debian, I think it might be
best to stick with Perl for uscan :).

> I do hope someone can implement it in perl and bring it to uscan. But
> it's hard for me to hack 4k lines perl.

I can understand that, and I’m not asking you to work on uscan — Osamu
already seems to be on that.

> Anyway, it's an exploration for using API rather than `git clone` locally.
> And I intend to get it to support more Git services, maybe gopkg.in,
> gitlab, etc.
> PS, gopkg.in will point to some specific branch, and
> github.com/<owner>/<repo>/tags doesn't work well even I append a
> '?after=<version>' suffix.
> >
> > 2. I have concerns regarding the scalability of such a service if we
> > actually adopted this approach: the GitHub quota permits 5000 requests
> per
> > hour (when authenticated). This sounds like a lot at first glance, but
> > consider that we already have 845 Go packages. Your code does 4 requests
> per
> > repository (IIUC), so already we are fairly close to reaching the limit,
> if
> > we don’t take any precautions.
> I haven't considered rate-limit, but do we check so frequently indeed?

I don’t actually know what the rate of uscan checks is behind the Debian
Package Tracker. I can imagine that other places do run uscan, too, though
(think Ubuntu, or other Debian derivatives). In fact, I’m working on a
dashboard myself which does run uscan fairly frequently.

Best regards,
Pkg-go-maintainers mailing list

Reply via email to