>>>>> On Tue, 3 Jan 2006 11:55:06 -0800, Tyler MacDonald <[EMAIL PROTECTED]> 
>>>>> said:

  >     Those modules were never approved... yet they're in 03modlist.data.
  > So what good is the "official" module list then? I was always under the
  > impression that it acted like a guardian, CPAN wouldn't allow you to
  > download a module that wasn't registered or wasn't uploaded by a registered
  > author, and that was supposed to prevent malice or accidents from happening
  > when somebody uploaded a module that was actually in somebody else's
  > namespace, or not approved.

There are two ways to reach maintainership status:
registration/approval and simple upload of a module in a namespace
that is not yet taken on a first-come-first-serve basis.

On CPAN you find two files:

  411682 Jan  3 21:10 02packages.details.txt.gz
  110183 Jan  3 19:49 03modlist.data.gz

As you say, 03xxx contains namespaces that have been registered and
went through some discussion of namespace issues and they have a
description line and a DSLIP entry (metadata about Development status,
Support level, Language used, Interface style, Public License). It
contains evensome namespaces that have been registered in advance and
that have never lead to a released module.

In addition, there is 02xxx that contains actual uploads where
registered and non-registered namespaces are mixed together.

In CPAN.pm you find both file contents merged. You can tell the
difference by watching if there is a description line and a DSLIP
entry.

Hope that helps,
-- 
andreas

Reply via email to