Re: What's the push to require the latest Perl?

2018-01-11 Thread Dave Horsfall
On Thu, 11 Jan 2018, Daniel J. Luke wrote: MacPorts doesn't support version comparisons in dependency specifications (this is a really old issue that's been discussed a lot over the years). Ah. I look forward to seeing your contributions! Maybe you will come up with a solution that no one

Re: What's the push to require the latest Perl?

2018-01-11 Thread Daniel J. Luke
On Jan 11, 2018, at 3:33 PM, Dave Horsfall wrote: > You might want to note that FreeBSD ports uses a ">=" test on versions e.g. > Perl 5.26 will satisfy the 5.24 requirement (unless, of course, there was the > aforesaid technical reason why it cannot). MacPorts doesn't

Re: What's the push to require the latest Perl?

2018-01-09 Thread Daniel J. Luke
On Jan 9, 2018, at 12:36 PM, Bill Cole wrote: >> On Jan 8, 2018, at 9:46 PM, Bill Cole >> wrote: >>> An issue with that is the fact that some amount of perl5 code in the wild >>> (often including

Re: What's the push to require the latest Perl?

2018-01-09 Thread Bill Cole
On 9 Jan 2018, at 10:30, Daniel J. Luke wrote: On Jan 8, 2018, at 9:46 PM, Bill Cole wrote: An issue with that is the fact that some amount of perl5 code in the wild (often including widely-used non-core modules) is broken with each major

Re: What's the push to require the latest Perl?

2018-01-09 Thread Daniel J. Luke
On Jan 8, 2018, at 9:46 PM, Bill Cole wrote: > An issue with that is the fact that some amount of perl5 code in the wild > (often including widely-used non-core modules) is broken with each major > version. This is why upstream maintains 2 major

Re: What's the push to require the latest Perl?

2018-01-08 Thread Daniel J. Luke
On Jan 8, 2018, at 1:36 PM, Bill Cole wrote: > I think a better approach would be to either require the p5-foo port OR > (better) require path:${perl5.lib}/Foo.pm:p5.${perl5.major}-foo or (best) > create a new syntax for dependencies that check

Re: What's the push to require the latest Perl?

2018-01-08 Thread Bill Cole
On 5 Jan 2018, at 5:45 (-0500), Ryan Schmidt wrote: There's no problem here. Just because ports use perl5.24 or perl5.26 for their own purposes has no bearing on what you use for your own personal projects. [...] Understood: Multiple Perl versions can co-exist and my fear of automated

Re: What's the push to require the latest Perl?

2018-01-05 Thread Ryan Schmidt
On Jan 5, 2018, at 17:49, Dave Horsfall wrote: > On Fri, 5 Jan 2018, Ryan Schmidt wrote: > >> If you have been using perl5.24 and p5.24 modules for your own projects and >> now want to use perl5.26, simply install the p5.26 versions of the modules >> you want. > > Err, why should a user have

Re: What's the push to require the latest Perl?

2018-01-05 Thread Dave Horsfall
On Fri, 5 Jan 2018, Ryan Schmidt wrote: If you have been using perl5.24 and p5.24 modules for your own projects and now want to use perl5.26, simply install the p5.26 versions of the modules you want. Err, why should a user have to waste disk space on two versions of Perl? Surely if a port

Re: What's the push to require the latest Perl?

2018-01-05 Thread Ryan Schmidt
There's no problem here. Just because ports use perl5.24 or perl5.26 for their own purposes has no bearing on what you use for your own personal projects. perl5.24 and perl5.26 install to different locations, do not conflict with one another, and can be simultaneously installed and used.

Re: What's the push to require the latest Perl?

2018-01-04 Thread Bill Cole
On 4 Jan 2018, at 4:53, Ryan Schmidt wrote: On Dec 30, 2017, at 20:27, Bill Cole wrote: [...] If anyone involved in making MacPorts policy can explain this coherently, I'd greatly appreciate it. What other explanation would you like? Well, I'm not entirely sure... I think I've figured

Re: What's the push to require the latest Perl?

2018-01-04 Thread Bill Cole
On 1 Jan 2018, at 14:55 (-0500), Craig Treleaven wrote: On Dec 31, 2017, at 11:46 PM, Bill Cole wrote: Ah, so apparently the reason this met total silence was that it got lost/dropped somewhere so only I thought it was posted. Odd... Reposted

Re: What's the push to require the latest Perl?

2018-01-04 Thread Ryan Schmidt
On Dec 30, 2017, at 20:27, Bill Cole wrote: > On 15 Dec 2017, at 18:00 (-0500), Bill Cole wrote: > >> In regards to https://trac.macports.org/ticket/55208 : > [...] >> Why would help2man demand the absolute latest Perl? Well, because the >> Portfile says it does. However, in the real world,

Re: What's the push to require the latest Perl?

2018-01-01 Thread Craig Treleaven
> On Dec 31, 2017, at 11:46 PM, Bill Cole > wrote: > > Ah, so apparently the reason this met total silence was that it got > lost/dropped somewhere so only I thought it was posted. Odd... > > Reposted message: > > From: Bill Cole

What's the push to require the latest Perl?

2017-12-31 Thread Bill Cole
Ah, so apparently the reason this met total silence was that it got lost/dropped somewhere so only I thought it was posted. Odd... Reposted message: From: Bill Cole To: macports-users@lists.macports.org Subject: What's the push to require the

Re: What's the push to require the latest Perl?

2017-12-30 Thread Bill Cole
On 15 Dec 2017, at 18:00 (-0500), Bill Cole wrote: In regards to https://trac.macports.org/ticket/55208 : [...] Why would help2man demand the absolute latest Perl? Well, because the Portfile says it does. However, in the real world, help2man is happy with any perl since 5.8. Doing a 'port