On 20 February 2012 11:30, Michael Meeks <michael.meeks@suse.com> wrote:
On Sun, 2012-02-19 at 14:39 +0000, Tim Retout wrote:
Great :-) thanks for that, it's always nice to use standard methods
instead of custom / hand-coded ones. Clearly we want to introduce new
perl dependencies on shared modules only with some care - it's nice
having solenv/ be reasonably self-contained.
Indeed - a useful tool is 'corelist', which will print the first
version of Perl which shipped a given CPAN module in the core:
$ corelist File::Spec
File::Spec was first released with perl 5.00405
(i.e. Perl 5.4)
Which leads to the question: what is the minimum version of Perl we
can rely on in LibreOffice? Currently configure.in checks for Perl 5,
but the Perl currently in solenv almost certainly requires Perl 5.8
(first released 2002).
Even Perl 5.10 (first released 2007) is no longer maintained upstream,
although it is still the one shipped in Debian squeeze/lenny (current
stable/oldstable):
http://www.cpan.org/src/
http://packages.debian.org/squeeze/perl
Would it be reasonable to bump the configure.in check to look for Perl
5.10, for now? I might try to replace the macro with one from the
autoconf archive:
http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=blob_plain;f=m4/ax_prog_perl_version.m4
Kind regards,
--
Tim Retout <tim@retout.co.uk>
Context
- Minimum Perl version requirement (was: Re: [PUSHED] Replace make_absolute_path with rel2abs in solenv) · Tim Retout
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.