Hi Linda!
On Sun, 12 Aug 2018 04:46:24 -0700
"Linda A. Walsh" wrote:
> Shlomi Fish wrote:
> > Hi all!
> > do you think I was being unreasonable, or should I as a CPAN
> > author/maintainer/adopter accommodate for people running old perl5s, in my
> > case 5.10.x and below:
> >
> >
> Going
Hi Rocco,
On Fri, 17 Aug 2018 13:28:03 -0400
Rocco Caputo wrote:
> On Aug 17, 2018, at 10:26, Shlomi Fish wrote:
> >
> > On Fri, 17 Aug 2018 08:19:26 -0500
> > Andy Lester wrote:
> >>
> >> I suggest that trying to optimize away complaining is a losing battle. You
> >> will never make
On Aug 17, 2018, at 10:26, Shlomi Fish wrote:
>
> On Fri, 17 Aug 2018 08:19:26 -0500
> Andy Lester wrote:
>>
>> I suggest that trying to optimize away complaining is a losing battle. You
>> will never make everyone happy.
>
> Good advice, but see the first item of
>
On Fri, 17 Aug 2018 08:19:26 -0500
Andy Lester wrote:
> > On Aug 17, 2018, at 4:41 AM, Shlomi Fish wrote:
> >
> > I see - in that case I suppose they can afford to either pay me, say 100 USD
> > per dist per year, so I'll support older versions of perl there - and for
> > everyone, or
Hi Paul!
Thanks for the reply.
On Sun, 12 Aug 2018 09:56:44 -0400
Paul Bennett wrote:
> I have faced this question head-on with some of my modules.
>
> My take is that there are many, many corporations version-locked to
> specific "enterprise-grade" Linux distros, and stuck with system Perls
On Sun, Aug 12, 2018 at 09:56:44AM -0400, Paul Bennett wrote:
> My take is that there are many, many corporations version-locked to
> specific "enterprise-grade" Linux distros, and stuck with system Perls
> maybe as old as 5.10, and potentially stuck with security policies that
> make solutions
Shlomi Fish wrote:
Hi all!
do you think I was being unreasonable, or should I as a CPAN
author/maintainer/adopter accommodate for people running old perl5s, in my case
5.10.x and below:
Going backwards it becomes more difficult to support an old version,
along with
older versions having
On Sat, Aug 11, 2018 at 4:39 PM Shlomi Fish wrote:
> Hi all!
>
> This post is a little flamebait, so please try to keep the discussion
> civil.
>
> Anyway, after reading the discussion in this public github issue, and
> following
> some of the links (especially
>
>
I have faced this question head-on with some of my modules.
My take is that there are many, many corporations version-locked to
specific "enterprise-grade" Linux distros, and stuck with system Perls
maybe as old as 5.10, and potentially stuck with security policies that
make solutions like
On Sun, 12 Aug 2018 13:41:54 +0200
Xavier Noria wrote:
> I’ve been out of the Perl community for many years, but to give you an
> example of the opposite trend, in Rails we drop support for old Ruby really
> fast. People need to move forward if they want to upgrade Rails (and
> culturally, they
Hi,
On Sun, 12 Aug 2018 09:33:59 +0100
Stephen Patterson wrote:
> Hi Shlomi
>
> It's been several years since I was last active in the Perl community, so
> take this with a good pinch of salt (I think 5.8 was new at the time) :)
>
> That being said, I remember each module having a
On Sun, 12 Aug 2018 13:41:54 +0200
Xavier Noria wrote:
> I’ve been out of the Perl community for many years, but to give you an
> example of the opposite trend, in Rails we drop support for old Ruby
> really fast. People need to move forward if they want to upgrade
> Rails (and culturally, they
I’ve been out of the Perl community for many years, but to give you an
example of the opposite trend, in Rails we drop support for old Ruby really
fast. People need to move forward if they want to upgrade Rails (and
culturally, they normally do).
Giving this example to subscribe something already
On Sat, 11 Aug 2018, Shlomi Fish wrote:
Hi all!
This post is a little flamebait, so please try to keep the discussion civil.
Anyway, after reading the discussion in this public github issue, and following
some of the links (especially
Hi Lars,
thanks for your comprehensive and informative reply.
On Sun, 12 Aug 2018 10:23:50 +0200
Lars Dɪᴇᴄᴋᴏᴡ 迪拉斯 wrote:
> I have read the posts linked in your message.
>
> > should I as a CPAN author/maintainer/adopter accommodate for people
> > running old perl5s
>
> It's your choice.
Hi Shlomi
It's been several years since I was last active in the Perl community, so
take this with a good pinch of salt (I think 5.8 was new at the time) :)
That being said, I remember each module having a dependencies file with the
minimum compatible perl version for that version of the module,
I have read the posts linked in your message.
> should I as a CPAN author/maintainer/adopter accommodate for people
> running old perl5s
It's your choice. You are in charge of the software, so you get to
decide. I'm certain that's how it's been generally handled in past, too.
Are you asking to
Hi all!
This post is a little flamebait, so please try to keep the discussion civil.
Anyway, after reading the discussion in this public github issue, and following
some of the links (especially
https://szabgab.com/what-does--if-it-aint-broke-dont-fix-it--really-mean.html ),
do you think I was
18 matches
Mail list logo