On Wed, Sep 03, 2014 at 12:44:41PM +0200, David Coppa wrote: > On Tue, Sep 2, 2014 at 10:07 PM, Stuart Henderson <[email protected]> wrote: > > On 2014/09/02 15:10, David Coppa wrote: > >> On Tue, Sep 2, 2014 at 2:31 PM, Jasper Lievisse Adriaanse > >> <[email protected]> wrote: > >> > >> > A list of results can be found here: http://portscout.jasper.la/ > >> > >> Very nice and useful! > > > > It is, though there are a few cases where it gets confused or can't handle > > things - > > one case is where upstream has multiple major versions on the go (like > > Asterisk), > > another is the increasingly common case of github-only releases. > > another case is hackage.haskell.org
As for Asterisk, you can use the PORTSCOUT variable to instruct portscout on how it should handle this particular port. I've added a handler for Github and Rubygems yesterday. The former because it was totally unhandled and the latter because robots.txt forbit portscout from crawling it. But they've got an API which can be queried for versions. I'm currently doing the same for CPAN as portscout would often resort to guessing versions for modules.. I'll put hackage on my list.
