Port trees for specific versions of MacOS

[Ken Cunningham]

On 2018-03-28, at 9:20 AM, René J.V. Bertin wrote:

> On Wednesday March 28 2018 09:00:52 Ken Cunningham wrote:
> 
> Thanks for picking this up,
> 
>> I'd just like to mention that I've been working on this on my own for a while now, and have such trees in place, and available for contributions.  Anyone interested, feel free to suggest or contribute, please.
> 
> How much extra work would you say this represents, assuming you only do the minimal corrective maintenance once ports get "frozen"?

So far, minimal extra work. The more things diverge in time, however, the more this might change.

Pegged ports are easy. They just stay pegged.

Pegged supporting libraries, like libvpx, are harder as often in the main port tree the use of them on certain systems is dropped -- can't ask for anything different. Interested users will have to step up.


> 
> Also, what's the exact approach? Do users of, say, 10.8 only specify the 10.8 overlay tree before the usual ports tree, or do they specify the whole series (say, 10.8 - 10.7 - 10.6)? The latter approach would dispense you of having to copy all those ports requiring C++11 in all overlays (but more could go wrong on user machines?)
> 

Open to opinion on the optimal method, but so far, I've set it up that each OS port tree overlay is freestanding, just to keep my mind clear.

It needs a bit of cleanup every once in a while, as things change in the main repo and I don't notice necessarily instantly.

Ken