Front page | perl.perl5.porters |
Postings from July 2016
I think, on the whole, a slightly more conservative approach might be more fruitful. Something like: 1) Apply a patch now that provides an option to remove '.' from @INC, but with the option disabled by default 2) Have some of us build perls with the option turned on and smoke ALL the things to figure out just how much fun this isn't going to be (because it's already clear that inc::latest, inc::Module::Install, t::lib and various other things that get used a bunch are going to die horribly). 3) Try and get the various toolchain stuff as robust against the various issues as possible, then repeat step 2 until things start to look sane(r) 4) Then, N blead releases onwards, switch the default to 'enabled', and see how many BBC reports we get in spite of our efforts in steps 2 and 3 5) Make a final choice for the next 5.even.0 release before the 'disruptive changes' lockdown based on the information from 4 and whatever downstream contacts we can scrape up to express opinions 6) (hopefully) Profit. -- Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue http://shadowcat.co.uk/blog/matt-s-trout/ http://twitter.com/shadowcat_mst/ Email me now on mst (at) shadowcat.co.uk and let's chat about how our CPAN commercial support, training and consultancy packages could help your team.Thread Previous