Front page | perl.perl5.porters |
Postings from February 2023
On Mon, 27 Feb 2023 at 14:47, Jeremy Hetzler <jeremyhetzler@gmail.com> wrote: > I wonder, is there any way to surface any of the existing > blead-breaks-CPAN information for module authors to use? > Not sure i follow about "for module authors to use". We have a group of volunteers, Andreas Koenig, Slaven Rezik, Carlos Guevara being notable examples, who try to build modules with blead perl as often as they can, and when they do they file BBC tickets. Some of them (Andreas and Slaven in particular) are kind enough to bisect the cause and include the commit that broke the BBC module. I know that from time to time they file tickets with module owners, and from time to time they file tickets with us. Depending I guess on whether they think the module is at fault or perl is. We call these tickets "BBC" tickets. You can search the open tickets on our issue tracker on github: https://github.com/Perl/perl5/issues?q=is%3Aissue+is%3Aopen+BBC Other people do the same but they build with the latest release, eg, perl 5.37.9. I am not sure if they use specific infra for this. Hopefully some of them will speak up. > > @demerphq, it seems like you have some way of knowing which CPAN > modules are broken by blead. Where does that information come from? > It is either via bug reports in our issue tracker, or by me manually trying to install things with cpanm and the latest perl. Often the latter happens as part of responding to the former. For instance, installing Dist::Zilla with the latest blead pulls in a lot of modules so it is a pretty good way to test a lot of stuff at once. > What would be the easiest way to just blat it onto a webpage that > module authors could access? > Not sure. I just came back from a 13 hour flight, and my jetlag is really kicking in now, so I might have better ideas tomorrow when I am more rested. cheers, Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"Thread Previous | Thread Next