hi all, what's status now? Should I play with -devel still or will it be switched to regular qt4-mac?
BTW is there any easy way how to replace qt4-mac with qt4-mac-devel without uninstalling/deactivating all qt4 deps apps, please? petr On Dec 15, 2011 (Thursday), at 2:26 PM, Ryan Schmidt wrote: > > On Dec 15, 2011, at 07:04, Michael Dickens wrote: > >> < http://blog.qt.nokia.com/2011/12/15/qt-4-8-libraries-released-stand-alone/ >> > >> < http://labs.qt.nokia.com/2011/12/15/qt-4-8-0-released/ > >> >> I'm pretty sure upgrading to 4.8.0 will break some of the current qt4-mac >> dependent ports -- a new point release invariably does. So, should I bump >> qt4-mac-devel first to 4.8.0 to let others do testing (etc), or just go >> straight for the gusto and bump qt4-mac and let the dust settle wherever it >> does? - MLD > > Updating qt4-mac-devel first is a good idea. OTOH, I'm not sure how many > people will actually test with that. > > If you update qt4-mac-devel, please take the opportunity to set its > dist_subdir to qt4-mac so it finally shares its distfiles with the qt4-mac > port. > > > > _______________________________________________ > macports-dev mailing list > macports-dev@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
