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
February 27, 2023 12:47
Re: Deprecation doesn't mean we have two release cycles beforethings break.
Message ID:
On Mon, 27 Feb 2023 at 13:01, G.W. Haywood via perl5-porters <> wrote:

> Hi there,
> On Mon, 27 Feb 2023, demerphq wrote:
> > On Mon, 27 Feb 2023 at 12:19, G.W. Haywood via perl5-porters wrote:
> >> On Mon, 27 Feb 2023, Dave Cross wrote:
> >>> On Mon, 27 Feb 2023 at 10:56, G.W. Haywood via perl5-porters wrote:
> >>>
> >>>>
> >>>> I'm the maintainer of exactly one CPAN module, but since it's used by
> >>>> both Sendmail and Postfix users I'm very keen to keep it working.  It
> >>>> would help me greatly in this effort if for example a row or two could
> >>>> be added to this table:
> >>>>
> >>>>
> >>>>
> >>>> to show development versions of Perl ...
> >>>
> >>> The top seven rows on that page already show the most recent
> development
> >>> versions of Perl. So I'm not really sure what more information you're
> >>> asking for.
> >>
> >> Sorry, maybe I misunderstand.
> >
> > I think you did. That tables lists released versions. Such tables would
> not
> > list every patch in blead.
> >
> >> Is one of those what you'd call 'blead'?
> >
> > No.
> In that case I don't I misunderstood - I think you did.  But that's
> probably because I'm unfamiliar with the terminology and don't know
> how to express my ideas so people on this list can understand them.
> > You would need to build perl from a checkout of the repo at
> >
> My point exactly.  And in my case, because of my pathological aversion
> to github (and github's aversion to my browser), I simply won't do it.

I dont understand what your browser has to do with it.

git clone
./Configure -Dusethreads -Doptimize=-O3 -d -Dusedevel
make -j16

Or maybe:

git clone
cd perl5
git pull
perlbrew uninstall latest_blead
perlbrew install --notest --noman --64all --as latest_blead --debug
--thread --multi -Doptimize=-g -Dusedevel -j 16 ./
cpanm Your::Favorite::Module

> > That wasn't my point however, my point was it would be helpful if folks
> > could take the time to build perl against the latest commit in the blead
> > branch on github and then test it against their favourite modules. If
> > anything doesn't build, file a patch with the author of the module and or
> > maybe with us as an issue.
> That's incredibly onerous.

I'm sorry you feel that way.  It's what all the people who work hard to
maintain perl do all the time.

> 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. There are tens of thousands of modules on CPAN, and we can merge
dozens of commits a day sometimes. It's a lot bigger of an undertaking than
you seem to realize.

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.


perl -Mre=debug -e "/just|another|perl|hacker/"

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