Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Perhaps his method of counting is flawed. But, in the interest of making the right thing more easy, perhaps this is an argument for perl folks to announce and advertise their software on more places than just CPAN. Having a centralized software repository like CPAN is great for a number of reasons, but one of its weaknesses is that it can't reach the people who don't know about it. If we announce our software in places like Fresmeat, it's possible that we can make it easier for non-perlers to discover and use our software.

    To make this easier and more common, I wonder if it would be reasonable to have a part of our toolchain hit the Freshmeat API after uploading to CPAN. That way, once an author prepares a tarball to push to CPAN, she can use the same Makefile or similar to alert freshmeat of a new release of her software if she desires.

    I think I'll go add a few pieces of perl software to freshmeat and investigate a way to make it easier to let freshmeat know when new versions arrive.

    • Great idea; I wish I'd thought to suggest that when I posted.

      • So why don't we announce all /pre-existing/ modules on Freshmeat, not just to flood them, but to emphasise the vast wealth of Perl code available?

        Jeezuz, someone could even write a Perl program to do that :-)))).

        Yeah, yeah, I know. Someone somewhere would blame the language, not the uploader.

        It's a pity Freshmeat and/or it's supporters see Freshmeat as the center of the universe, as if a Perl user would look there first anyway, or ever.