No Perl/CPAN

Issue #41 resolved
James Wright created an issue

No description provided.

Comments (12)

  1. Glenn Proctor Account Deactivated

    Any updates on Perl support (specifically CPAN)? We have a significant chunk of legacy Perl which won't be going away any time soon, and it would be great to have that covered by VersionEye as well as our Python/Ruby/JS stuff.

  2. Hari Sekhon

    Me too, curious to see how this will look as there is no Pip requirements or Maven pom equivalent standard to test (I personally script usage of a cpan-requirements.txt file, one package per line with standard hash commented lines).

  3. Hari Sekhon

    I used cpanm for all my builds but don't recall seeing cpanfile (or perhaps I just didn't register it as a standard so skipped over it, whereas I Travis CI forced me use cpanm).

    I ended up emulating pip's requirements.txt which seems simpler, but will switch to this format instead to make use of this if this new versioneye functionality.

    Look forward to testing the new functionality, thanks for working on this!

  4. Glenn Proctor Account Deactivated

    Hi all

    Any updates on the status of Perl support, and what it will require (cpanfiles or whatever)?

    Glenn.

  5. Timo Sulg

    Hi, I think it would be some point next week in production .

    Today i finished refactoring old implementation of CpanCrawler, but there's still a couple of things to do. But we've other high priority tasks before we can tackle the last remaining part.

    Overall it'll require cpanfiles as it's only official looking specification i was able to find: https://metacpan.org/pod/cpanfile we can also add specialized parser based on customer requirements as long it has a way to resolve name of dependency and required version.

    Cheers

  6. Glenn Proctor Account Deactivated

    Excellent, thanks for the update. cpanfiles looks like the best approach.

    Glenn.

  7. Log in to comment