in reply to Proposal: change in the [cpan://module] shortcut

What about [cpan://Foo::Bar]? That wouldn't neccessarily translate to http://search.cpan.org/dist/Foo-Bar/ and http://search.cpan.org/dist/Foo::Bar/ doesn't exactly make sense (not to mention that it actually misses the module Foo::Bar)

I'd be content with cpan:// remaining the same, and cpand:// generating the dist shortcut, and cpana:// generating a search for all, and cpanp:// generating a pod shortcut ( http://search.cpan.org/perldoc?module::name ).

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

  • Comment on Re: Proposal: change in the [cpan://module] shortcut

Replies are listed 'Best First'.
Re: Re: Proposal: change in the [cpan://module] shortcut
by mirod (Canon) on Feb 16, 2004 at 15:10 UTC

    When wouldn't [cpan://Foo::Bar] translate into http://search.cpan.org/dist/Foo-Bar/? When the module is not a distribution? First this probably doesn't happen that often ,and then, as Corion noted, search.cpan.org itself takes care of this and returns the link as it is now.

    In this case I would not like to give the option, as it would lead to "link dilution": instead of all references pointing to a single page we would have several targets, which would not help Google ranking as much.

        I care about Google rankings because if you look for perl+<whatever_keyword> in Google, chances are that you are never going to find the CPAN module(s) that would help you. Just try it (perl+cgi is quite scary ;--(. The current situation is that if you know CPAN and if you are ready to spend some time either here or on the newsgroups or in some mailing list, then you are going to use the right tool for the job. I would like to increase the likelihood for users who do not have that kind of time and who simply use Google to get to the same point.

        So I think your objection is valid, but only up to a point: if you are looking for Tk::Frame, then the link I propose gives you Tk as the third result. If you know what you are looking, then chances are that you are going to find it. BTW Tk is an example where googling for tt>perl+tk takes you to the Perl/Tk site which looks like the right place to go.