On Fri, Sep 24, 2010 at 13:47, Randal L. Schwartz <merlyn@xxxxxxxxxxxxxx> wrote:
>>>>>> "Ãvar" == Ãvar ArnfjÃrà Bjarmason <avarab@xxxxxxxxx> writes:
>
> Ãvar> Since we're not getting patches for common things that have been
> Ãvar> broken on 5.6 for years and bumping the requirenment to an 8 year old
> Ãvar> perl (5.8) instead of a 10 year old one (5.6) would make things much
> Ãvar> easier, including:
>
> Ãvar> Â* Fixing the perl/ Makefile mess
>
> Ãvar> Â* Being able to use 5.8 features
>
> Ãvar> Â* Being able to honestly support the 5.8 release, 5.6 doesn't even
> Ãvar> Â Âcompile on modern systems without undocumented monkeypatches, and
> Ãvar> Â Âfew people use it so we don't get fixes for it.
>
> Ãvar> I'd like to propose dropping 5.6 support, and move to say 5.008. I can
> Ãvar> do the work required to add appropriate docs / use statements and
> Ãvar> fixes to bugs that we can't fix on 5.6.
>
> As the token resident Perl expert, I'd be completely fine with that.
> Sane choice.
>
> It might be useful to document that by adding:
>
> Ârequire 5.008;
Right, except that should be `use 5.008`. Since you don't want to run
anything else within an implicit or explicit BEGIN block before perl
fails on that. E.g. `require 5.008; use Digest::MD5;` would just spew
an error about Digest::MD5.
The only reason you'd want `require $version' is if you care about
5.005, but even then you can do `BEGIN { require 5.008 }`.
--
To unsubscribe from this list: 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