khemir nadim wrote:[snip]
[snip]could someone, please, tell me how some modules get meta data like "module
is a devloper release" and the DLSIP definitions so I can get some of my
modules listed on search.cpan.org. All this information must be right in
front of me but it seems I have a temporary doc blindness.
I'm also curious about how many made the move to Module::Build.
For the meta information, upgrade to a new ExtUtils::ModuleMaker.
I believe that the meta-information the OP is asking about is the stuff set/updated with 'Register Namespace' and 'Edit Module Metadata' on PAUSE. Although I'm not sure how active the module list is these days in approving things.
Not that there is anything wrong with updating ExtUtils::ModuleMaker and getting a META.yml file too :-)
I've used Module::Build in a few modules that I've released. It's
smashing, once you've got shell aliases for "perl Build test verbose=1",
etc (`make test' was SO much quicker to type ;-)).
To be fair 'make test TEST_VERBOSE=1' isn't that much quicker :-)
It introduces another dependancy, but IMHO it's well worth it for dropping the dependancy on a local Makefile guru.
I second that opinion (although there are currently some problems with the current version of M::B on cgiwin platforms). I use it for one of my CPAN modules and will move my others to it when time allows. I would recommend using Module::Build::Compat to build a Makefile.PL if you're planning on throwing it at CPAN.
There are quite a few distributions using M::B already (Over 150 in late 2003. probably more now).
Cheers,
Adrian
