Re: Changed ISPMan Installation

Jörg Delker wrote:

> The problem is, ISPMan has (IMHO) to provide a reference for perl libs 
> that are proven to work with that specific release.
> Now, I had the same idea to just fetch them via wget, but I figured 
> that some (older) releases were not downloadable from CPAN any more.
> Although this is no problem with current releases, it may render an 
> ISPMan release unusable/uninstallable over time eventually.
>
> So finally, I was just left with the choice of bundling the perl libs 
> with ispman.

I remember wondering about this a long time ago when I took over 
maintenance of a CPAN module. All the CPAN mirrors keep the last couple 
revisions of each package around for a while. Eventually (after a year 
or two or more) they'll get deleted, but the old versions are still around:

http://history.perl.org/backpan/
http://cpan.org/misc/cpan-faq.html#Where_older_Perl

I understand the worry of a newer dependency breaking ISPMan, but in my 
5+ years of doing Perl development using the latest versions from 
CPAN/Debian I can't remember something breaking. Sometimes an API 
changes, but typically it only bites me in situations such as when I 
neglected to read the "deprecated" section of the perldoc closely. Or 
maybe I'm just lucky :-)

What I've seen some perl apps do is require a minimum $VERSION of a 
loaded package that is known to work. For example:

use CGI 3.04;
# will die with 3.03 but will load >= 3.04

Just some more thoughts.

Regards,

Wim



-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285