develooper Front page | perl.perl5.porters | Postings from February 2023

Re: Deprecation doesn't mean we have two release cycles beforethings break.

Thread Previous | Thread Next
"G.W. Haywood" via perl5-porters
February 27, 2023 14:28
Re: Deprecation doesn't mean we have two release cycles beforethings break.
Message ID:
Hi there,

On Mon, 27 Feb 2023, demerphq wrote:
> On Mon, 27 Feb 2023 at 13:01, G.W. Haywood via perl5-porters wrote:
>> ... That's incredibly onerous.
> I'm sorry you feel that way.

Please understand that I don't feel that way because it causes me any
extra work.  It doesn't.  I feel that way because it seems to me that
you're asking people to do work which isn't necessary.  Wasteful, even.

> It's what all the people who work hard to maintain perl do all the time.

I'm sure you're right.  I'm trying to eliminate some of the burden.

>> Can't you just get the patched version(s) of Perl into cpan-testers
>> and get everything tested automatically by the next morning,
>> together with a nice page of idiot lights which show Where Things
>> Failed?
> IMO no.

Why not?

> There are tens of thousands of modules on CPAN ...

That was kinda my point.  You either get a few people (if you're very
lucky, apparently most people won't bother) to do a Perl build on some
random machine/architecture, over which you have no control, then test
it by building a few random modules (which seems to me like dropping
bombs from an Avro Manchester in WWII[*]), or you get a single person
to do pretty much the same job once, except CPAN test machines can now
use the new Perl to build tens of thousands of modules on a bunch of
different architectures, automatically, within a few hours, more or
less for free.  Maybe they'll even mail you a report.

Isn't that going to be a much more useful exercise?  It doesn't have
to be after every patch, every day, of course.  Just pick some version
ad hoc which seems reasonable to the people doing the development.

> On the other hand, pulling the latest code, and then using perlbrew to
> build it and install it locally and then using cpanm to install your
> favorite dependencies is not that difficult.

Isn't it just as easy to do that on the machine that runs CPAN testers?

Explain to my satisfaction why it isn't and I'll go away.  I just want
for you to give the blead Perls some really good exercise within hours
of a commit instead of everybody waiting for (your estimated) couple
of years for it to hit the fan.

[*] About 5% of the bombs landed within five miles of the target.



Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About