On Fri, 18 Nov 2005, John Siracusa wrote:
On 11/18/05, Randy Kobes <[EMAIL PROTECTED]> wrote:What looks like is happening is that search.cpan.org (sometimes) converts links in the docs into things of the form http://search.cpan.org/perldoc?Module::Name This seems to work if Module::Name is a registered name (eg, a query in CPAN.pm turns up some information on it), but doesn't for modules (or pure pod files) like Rose::DB::Object::Tutorial for which CPAN.pm doesn't know anything about (ie, it doesn't appear in the CPAN/PAUSE indices).Hm, okay, two questions. First, what do I do about it? Make the .pod into a .pm instead? That seems...icky. Second, why does this kind of linking work elsewhere? Example: The page: http://search.cpan.org/dist/Catalyst/lib/Catalyst.pm The source: http://search.cpan.org/src/MRAMBERG/Catalyst-5.56/lib/Catalyst.pm which contains the text: See L<Catalyst::Manual::Intro> for additional information. Which correctly links to: http://search.cpan.org/~mramberg/Catalyst-5.56/lib/Catalyst/Manual/Intro.pod Puzzling...
It is puzzling ... One difference between the example of Catalyst::Manual::Intro and Rose::DB::Object::Tutorial is that Catalyst::Manual::Intro has a =head1 NAME Catalyst::Manual::Intro - Introduction to Catalyst section, whereas Rose::DB::Object::Tutorial doesn't. Perhaps inserting such a section would help - what seems to happen is that, within a distribution, direct links to docs will be formed for modules within that distribution; otherwise, http://search.cpan.org/perdoc? will be used. Although a NAME section alone isn't enough to register a module in the CPAN/PAUSE indices (a package declaration would also be needed, for example), perhaps such a section is enough for search.cpan.org in the context of forming links. -- best regards, randy
