On Jun 26, 2012, at 21:46, Joshua Root wrote: > On 2012-6-27 11:38 , Ryan Schmidt wrote: >> Now that I've caught up on the commits and other messages of the day, I >> understand what's going on. A major change just took place for all of perl >> in MacPorts in r94655. This needed to be done, but it included a change to >> the perl5 portgroup that is incompatible with how that portgroup was used >> before: the perl5.branches option was removed; previous p5 ports relied on >> that option existing. So as with the previous time that we did a massive >> overhaul of perl in MacPorts two years ago, the existing perl5 1.0 portgroup >> should have been kept intact and a new perl5 1.1 portgroup created with >> these changes, to avoid these warning messages. >> >> Thankfully in this case the warnings are harmless and should just be ignored: >> >> http://lists.macosforge.org/pipermail/macports-users/2012-June/029578.html > > I guess we could put the default back for a while if the warning is > confusing people.
I think it will confuse people and cause them to email the list or file tickets. At least there's a canonical response we can point them to on the users list now. But if we can easily prevent the warning by putting a perl5.branches default (empty?) into the portgroup that would be nice. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
