I mean, would not a better more efficient method be to create a list of your requested ports and just migrate those?
On Sun, Oct 19, 2014 at 2:52 PM, Carlo Tambuatco <oraclmas...@gmail.com> wrote: > Even if the old ports that are dependencies of the old port still exist, > the upgraded port with the new dependencies downloads and builds the new > dependencies before it upgrades itself. Even if this process accumulates > useless or redundant ports over time, it should not affect the build of the > newer ports, right? > > On Sun, Oct 19, 2014 at 2:43 PM, Brandon Allbery <allber...@gmail.com> > wrote: > >> On Sun, Oct 19, 2014 at 2:42 PM, Carlo Tambuatco <oraclmas...@gmail.com> >> wrote: >> >>> When you upgrade a port, everything it depends on gets updated first, >>> right? What doesn't get upgraded should not affect what does get upgraded >>> during the configure/build/install/activate phase, right? So how is using >>> -u different from uninstalling everything and reinstalling everything again? >>> >> >> When the new version of a port has different dependencies from the old >> version. >> >> -- >> brandon s allbery kf8nh sine nomine >> associates >> allber...@gmail.com >> ballb...@sinenomine.net >> unix, openafs, kerberos, infrastructure, xmonad >> http://sinenomine.net >> > >
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
