Front page | perl.perl5.porters |
Postings from February 2023
On Mon, Feb 27, 2023 at 7:47 AM demerphq <demerphq@gmail.com> wrote: > >> >> > 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. > I wonder, is there any way to surface any of the existing blead-breaks-CPAN information for module authors to use? @demerphq, it seems like you have some way of knowing which CPAN modules are broken by blead. Where does that information come from? What would be the easiest way to just blat it onto a webpage that module authors could access? -- Thanks, Jeremy Hetzler (he/him)Thread Previous | Thread Next