On Sat, Apr 10, 2021 at 8:28 PM Asher Gordon <asd...@posteo.net> wrote:

> Hello,
>
> I've noticed that the MetaCPAN page for many modules on CPAN has links
> to homepages and/or git/hg/etc. repositories. I assume these links are
> generated from the 'resources' field in the meta specification
> (META.json or META.yml), right?
>

Correct. The issue tracker defaults to the auto-generated tracker on
https://rt.cpan.org/ if none is specified; the others have no default.


> If I want the homepage, bugtracker, etc. to be the ones provided by
> MetaCPAN and CPAN, it would be redundant to specify them in the meta
> spec, no? And also, should I provide 'resources.license'? Dist::Zilla
> doesn't seem to do that by default despite knowing the license of the
> project and URL to the license.
>

MetaCPAN and CPAN do not provide any of these things, only the RT issue
tracker would be assumed if you don't specify any. The homepage field is
primarily useful if there is a website relevant to the distribution
separate from its documentation/repository/issue tracker.

Feel free to specify the license field in resources, but it is just for
URLs to license text which is not necessary if you provide the text of your
licenses in the distribution, as most dzil dists do automatically. The top
level license array is where the license(s) of the distribution is
specified.

-Dan

Reply via email to