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.

use Perl

All the Perl that's Practical to Extract and Report

Tagging CPAN changes More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Re: Tagging CPAN changes (Score:1)

by Corion (7288)

I'd like an RSS feed (or whatnot) that keeps me up to date on changes to modules on my watchlist (likely, modules I have installed or I have as a prerequisite to my releases), so a machine parser for Changes files is something I'm interested in. I'm definitively in the "free format text file" camp. I'm not really against POD, but I'm against human-unreadable formats like RDF, because IMO the Changes file is still mostly for humans to consume and mostly written by humans too. At least my releases "should" be
- Re: Tagging CPAN changes (Score:2)
  
  by miyagawa (1653) on 2007.11.07 4:11 (#58866) Homepage Journal
  
  I agree with you on most of the point. Actually I'm currently working on a tool to subscribe to RSS feeds of all modules (thanks to CPAN Recent Changes) we use on TypePad/Vox, and then run a qiuck regular expression like /api change/ or /security|vulnerabiltiy|serious bug/ etc. to quickly find out if we should upgrade or not. [unknownplace.org]
  
  Reply to This
  
  Parent
  - Re: (Score:2)
    
    by miyagawa (1653)
    
    Oops, the closing tag was misplaced, and also the URL was wrong. Correct Link [unknownplace.org].

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.