Hi folks,
While I agree with dmacks that we can't really automate this, I still think it's important to deal with. I think that if we support a perl version, we ideally want every variant to support that version. There are a few ways this could be accomplished:
1. Usually it's not considered especially polite to modify another maintainer's package. I think we should explicitly say that adding a new perl variant to another maintainer's package is ok, if it doesn't require any non-trivial changes.
I'm ok with this, as long as they tested the package under the new version.
2. We may want to have a policy that all perl packages with variants should be tested with all supported perl versions, assuming dependencies allow it. Or, we could require this only on entry to stable.
I maintain many different versions of Perl (5.6.1, 5.6.2, 5.8.0, 5.8.2, 5.8.3, 5.8.4, 5.8.5 and 5.8.6) for my own open-source project and I do find on a regular basis that a new version of Perl will break at least one Perl module out of the 172 Perl modules that I install. So I agree that all modules should be tested and if a module breaks, a report goes to rt.cpan.org.
Regards, Blair
-- Blair Zajac <[EMAIL PROTECTED]> Plots of your system's performance - http://www.orcaware.com/orca/
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
