ryandesign at macports.org
Sat Apr 11 03:27:36 PDT 2015
On Apr 11, 2015, at 5:13 AM, René J.V. Bertin wrote:
> On Friday April 10 2015 17:28:24 Ryan Schmidt wrote:
>> If you use default prefix, and use default variants for most ports, you'll get binaries for many of them, so if your internet connection is reasonably fast,
> I have wine installed, which means I get a ****load of universal variants that I would otherwise be able to avoid, including a number of big ones like ffmpeg and gtk . KDE ports provide their documentation through a variant, so most of those will be built from source too (even those I don't run personal versions of). So I have everything to gain by any kind of possibility that would allow me to prepare the migration as far as that's possible.
>> take stock of the ports you've installed any maybe cull some you don't need anymore.
> I do that periodically when I see the footprint on disk. It's rare though that I can really cull anything that makes a difference.
>> I'm not going to discuss ways of circumventing the migration strategy.
> I'm not planning to circumvent the underlying principle of rebuilding, just trying to find out to what extent rebuilding against the newer SDK can be done "prematurely", spreading out the computing time and resources, and evidently not with ports that contain OS-specific code, variants or whatever.
> I did this step for the 10.6 -> 10.9 upgrade in a VM ... I'll probably be adapting to 10.10 in a VM too (for lack of a 2nd Mac or Hackintosh) and just might see how far I'll get with applying the migration guide step by step, as part of a selfupdate (which I haven't been doing since january or so...)
I don't know that you can pre-build things for 10.10 while still on 10.9. Not in a way that I'm prepared to provide support for, anyway. What you can do though is upgrade ports one at a time after you upgrade to 10.10, instead of uninstalling them all and then reinstalling them all. This can lead to problems, but if you're aware of that and do it the right way (upgrade ports in dependency order) and know what to do when you encounter errors, it can work; it's what I did. Software built on 10.9 largely works fine on 10.10, so you can still use most of your old ports until you rebuild them. I still have a few ports installed on 10.10 that were built for 10.9 -- mostly those that cannot be built on 10.10 right now.
More information about the macports-users