Re: Are all CPAN modules supposed to be listed on metacpan.org?

Hi Tim!

Tim Landscheidt <tim@tim-landscheidt.de> writes:

Hi,
>
I'm looking into broken URLs of Fedora packages of (inter
alia) CPAN modules, in the following picking
https://src.fedoraproject.org/rpms/perl-Config-IniHash as a
random example.
>
This Fedora package refers to
https://metacpan.org/release/Config-IniHash which redirects
to https://metacpan.org/dist/Config-IniHash which is 404.
>
The source URL however,
https://cpan.metacpan.org/authors/id/J/JE/JENDA/Config-IniHash-3.01.01.tar.gz,
works nicely, as does some metadata file at
https://www.cpan.org/modules/by-authors/id/J/JE/JENDA/Config-IniHash-3.01.01.meta.

This use an old standard for the META-spec, which should not be a
problem.  (I have a very old one also using 1.2 without problems as
well.)  But the 1st line looks a bit incomplete as the spec says:

|The first line of a META.yml file should be a valid YAML document
|header like "--- #YAML:1.0".

Maybe that's the problem?  (Just a wild guess as I'm not really familiar
with the old spec's details.)

If an author releases a new module (or new version) on PAUSE, an indexer
analyses the package including the META-spec (and usually sends a mail
to the author that everything went well, what it indexed etc.).  But
this process can sometimes fail and the author has to restart it
manually.  (I never had any problems though, I just read about it.)

Does the module author have to click some button to trigger the
inclusion in the database?

Normally it gets added fully automatically, if the META-spec is correct
and the PAUSE server don't run into problems.

Are all modules available at cpan.org supposed to be listed at
metacpan.org?

At least those that appear as "name" in the META-spec, yes.

Just my 2 cents.

Best regards, Thomas
--
Address is only valid for short time!