Front page | perl.module-authors |
Postings from April 2008
I was looking to do some work with RPM's in perl. The CPAN modules for dealing with RPMs are in a bit of a mess. I'm wondering if there shouldn't be a way of 'voting a module off the island (CPAN)' if it outdated and no longer supported. The more outdated, broken and unsupported modules there are on CPAN, the less CPAN, as a whole, is useful to the community. It provides too many "blind allies", "false starts"...etc. Just to "wade" through all of the obsolete and/or no longer supported modules wastes alot of time -- besides having to install the module and possibly address build issues, you have to have some "clue" how to use the RPM (the documentation is often a "shorthand" that someone within that CPAN module-project would "just know", but is hard to make sense of without already being a user of the module). By the time I figure out how to use it and get around my misunderstandings of the documentation, I maybe then learn that the module either doesn't do the functions I need, or is *way* broken and not supported or is just plain obsolete and shouldn't have been expired from an online API library. Now I'd always reluctant to delete old code of my own -- I archive it thinking I may want to refer back to it, but if it is a snippet (or Module) of code that doesn't work anymore and I don't want to fix it, then I put it in an archive directory where I know I have old-broken code snippets. But I wouldn't have it in my /bin dir, or my "/scripts" dir (either system or personal) as an example of some way to do something. Nor would I offer it up to others as a Modular solution to someone's problems. Ideally, they'd be moved out of the CPAN namespace as well as being archived -- as they just waste time and space as people are forced to search through old broken code-snippets and modules to try to find something that works... Has this issue been raised before? -lindaThread Next