Maybe wait a little longer? In my experience it takes about a half to two days for a new module to show up on the CPAN index.

Anyway, I don't use META.yaml (AFAIK it gets automatically created by the cpan site). what I do is use CVS and put this in my modules:

our $VERSION = sprintf("%d.%03d", '$Name: $' =~ /(\d+)_(\d+)/,0,0);
And this in my Makefile.PLs:
WriteMakefile( # ... 'VERSION_FROM' => 'Module.pm' # filename to get version from # ... );

Then when I want to make a release, I tag the tree with a version number and some optional stuff:

> cvs tag v1_23-some-extra-info-that-gets-ignored
and run my release.sh script:
#!/bin/sh BUILDDIR=/tmp MODULE=my-distibution-name if [ ! -n "$1" ]; then echo "Use 'release.sh TAGNAME' to make a release"; exit 1; fi cd $BUILDDIR && rm -rf $MODULE && cvs export -r $1 $MODULE && cd $MODULE && perl Makefile.PL && make distcheck && make test && make dist && echo " +All done"

and presto! The "$Name: $" string in Module.pm will be replaced by "$Name: v1_23-some-extra-info-that-gets-ignored $" and will I have a working release tar ball in my /tmp/ directory.

By the way: the $Name: $ substitution only works if you check out the tree with the given tag name. One of the reasons for the release.sh script is that I used to forget that.


In reply to Re: CPAN indexing fu by Joost
in thread CPAN indexing fu by fluffy

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.