>>>>> On Wed, 2 Apr 2003 12:02:34 +0200, Elizabeth Mattijsen <[EMAIL PROTECTED]> said:
>> It means that the PAUSE indexer does not pick up the namespaces >> "threads" and "threads::shared" that are contained in your files >> lib/forks.pm and lib/forks/shared.pm respectively. > Ok, does this have to do with search.cpan.org? Not directly. The namespace index on PAUSE is CPAN/modules/02packages.details.txt.gz. I don't know how exactly this index influences search.cpan.org. >> If you visit the >> "View Permission" page on PAUSE, you find out that these two >> namespaces are co-owned by Artur and Jarkko. >> If this is what you want, all is OK, you need not react to this email. > Well, I don't want to update the "real" threads.pm and > threads::shared.pm, but I would like people to find forks.pm if > they're looking for threads.pm You mean, if people ask CPAN.pm to update threads, they should actually get forks.pm? If you want that, you need to ask Artur and Jarkko if they make you co-maintainer. To me this looks dangerous. The PAUSE indexer has a 1 to 1 mapping of namespaces to distributions, i.e. only one file on CPAN can be mapped to a given namespace. search.cpan.org is a different beast. It can list unlimited documents associated with a given query term. >> Please let me know how the wording of the notification could be >> improved to avoid confusion. > I'm still confused as to what "indexed" means in this context, so I > can't suggest an alternate wording (yet)... % zcat 02packages.details.txt.gz | head File: 02packages.details.txt URL: http://www.perl.com/CPAN/modules/02packages.details.txt Description: Package names found in directory $CPAN/authors/id/ Columns: package name, version, path Intended-For: Automated fetch routines, namespace documentation. Written-By: Id: mldistwatch 330 2003-03-31 12:22:25Z k Line-Count: 17653 Last-Updated: Wed, 02 Apr 2003 09:41:32 GMT A::B undef M/MA/MARCEL/Devel-SearchINC-0.01.tar.gz >> > And what should I put in a META.yml file to prevent this problem >> > (if at all possible?). >> META.yml support is currently in preparation. I don't know when it >> will start to influence the indexer. > Ok, maybe then it should not say that it didn't find a META.yml file, > as that _is_ confusing at the current time... Fair enough. Fixed. -- andreas
