Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
bigint search #1164
when searching for
If we look at -> https://metacpan.org/author/FLORA there is no bignum
but here it is on CPAN http://search.cpan.org/~flora/bignum-0.32/lib/bigint.pm
oalders new issue as per your instruction, sorry for the delay in doing so.
Perhaps this is because the latest release of bignum (which contains bigint) is an unauthorized release by a different author:
This is also screwing up FLORA's module list page. It should still show .32 for bignum in his list:
But does not since bignum-0.37 belongs to PJACKLAM. (Shouldn't bignum-0.37 show a big "UNAUTHORIZED RELEASE" warning?)
Likely adding to the confusion is that, as of Sun, 11 May 2014 10:41:02 GMT,
The dist is unauthorized according to the API:
So there must still be a bug about marking the dist as
There also doesn't appear to be code in the web ui about displaying authorized status.
The heuristic I'd suggest is to take the 'king module' of a dist - i.e. if somebody ships DBIx-Class and they're authorized for DBIx::Class, they're probably supposed to be able to ship the whole thing. Noting 'permission issue' or something-or-other for partially authorized dists is good, but it's common enough for a couple of modules deep in a namespace to get missed when distributing co-maint that you don't want to slap the big UNAUTHORIZED label on them just for that and you certainly don't want to exclude them from being the latest