On, 04 Dec 2003 12:40:25 -0800 Stas Bekman <[EMAIL PROTECTED]> wrote:
Hi, >Nice. I'd grep .pm files too, if changes don't contain the reference to this >change. Sure (waiting for META.yml... :-)) >I haven't used it myself with mp2. Does it work just fine? Me too (not yet). But the Changes reports mp2 notes from 0.90_02 release. >bi-weekly is probably better. OK >We used to have an explicit list, but as with time it was neglected, it was >abandoned: http://perl.apache.org/products/old-modules-categorized.html >If someone decides to fix and maintain it that would be great. I can do it. >If this is done >it can have a status column telling whether it's mp2 or mp1 complient. And >then you only need to poll for unknown modules or those who weren't mp2 compiled. I've already set up a simpe DB table containing this info about Apache::* modules. So, I must populate manually remaining mod_perl modules which doesn't live under Apache::* namespace. >> 3. The report is strictly tied to description in Changes distribution files >True. But this can be polished with time. [...] >That's where META.yml kicks in. I'm not sure which tag can we use though. >http://module-build.sourceforge.net/META-spec.html >but eventually that's what we are going to use. Using META.yml is a good thing, but we know when this will be a standard in CPAN distributions? In the meantime, we could be update the docs in order to encourage use of META.yml (as you suggested) or to report mp2 compatibility status in Changes file. >> 2) Apache::AuthPerLDAP - Again CPAN reports: >>[...] >> CPAN_VERSION 0.5 >>[...] >> instead of version 2.01 >Shannon, you ported the two, do you co-own the namespace of these modules? If >not this may explain why CPAN.pm doesn't show them. Enrico, search.cpan.org >does show the latest version. Yes, I've seen, even if www.cpan.org doesn't show them. by - Enrico -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
