Re: Some questions regarding MacPorts legacy support package

On Sun, Jul 5, 2020 at 6:15 PM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > > On Jul 5, 2020, at 3:03 PM, Jason Liu wrote: > > If a year or so sounds long, don’t worry. I wrote up the first version of >> legacysupport as “SnowLeopardFixes” in 2016, and it did not get really >> adopt

Re: Some questions regarding MacPorts legacy support package

On Sun, Jul 5, 2020 at 6:15 PM Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > > On Jul 5, 2020, at 3:03 PM, Jason Liu wrote: > > If a year or so sounds long, don’t worry. I wrote up the first version of >> legacysupport as “SnowLeopardFixes” in 2016, and it did not get really >> adopt

Re: Some questions regarding MacPorts legacy support package

> On Jul 5, 2020, at 3:03 PM, Jason Liu wrote: > > > Other than using the __MACPORTS_LEGACY_SUPPORT_APPKIT__ macro, is there some > way of making it optional? It will have to be specifically disabled by default, and then turned out optionally with some new legacysupport toggle that I/we in

Re: Some questions regarding MacPorts legacy support package

> > This will be — something new. Nobody actually knows how well this will > work. > Then I guess we're all going to find out the answer in the course of adding this new piece, huh? :P > It probably might best be something optionally used rather than a default > in legacysupport, as the opportun

Re: Some questions regarding MacPorts legacy support package

On Jul 4, 2020, at 15:44, Jason Liu wrote: > Question 2: > > A related question is that in MacportsLegacySupport.h, you guys use version > numbers such as 101300, 1070, etc. instead of the constants that are defined > in AvailabilityMacros.h, such as MAC_OS_X_VERSION_10_13, > MAC_OS_X_VERSI

Re: Some questions regarding MacPorts legacy support package

> Some questions regarding MacPorts legacy support package > > Jason Liu jasonliu at umich.edu  >