Hi, On Sun, 25 Jun 2006, Junio C Hamano wrote: > I vaguely recall that last time we discussed the minimum Perl > version requirement somebody perhaps Merlyn said 5.6 is old > enough but in some corporate settings people may still be stuck > with 5.004. > > Tentatively let's say our cut-off point is somewhere around 5.6. > If we can get away without relying on extra from CPAN that would > be great. Otherwise as long as the modules from CPAN we end up > depending on are all compatible with the cut-off version of Perl > that would be acceptable. We might even try to be nicer and > carry a straight copy of what we require from CPAN in compat/ > just like we have subprocess.py there (modulo licensing worries > if any, of course). I can live with it. Although I still think that it would be a good idea to convert (at least the most commonly used) scripts to C. Perl, Python and sometimes even bash are good for fast prototyping. But for serious work, such as profiling, they are not that good. And you can see different behaviour on different platforms (plus things like the SunCC requirement for XS on Solaris), which make the scripts less robust. Ciao, Dscho - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html