I haven’t dug into the code, but that’s a good idea. My worry would be things that XCode gives that are hard to build ourselves like AppKit w/ Swift 4.1.
It’s already 10.12 because it will not build in XCode 8 at all. If they use @available or whatever that could be the problem too. Which is a shame since 10.10 is still pretty modern. It’s getting old, but it’s only n-3 A big worry I have is if the project moves to XCode 10, it will only build on 10.14 very soon even if it will run all the way back to 10.10 —Mark On Sat, Jul 28, 2018 at 5:32 PM Christopher Jones <jon...@hep.phy.cam.ac.uk> wrote: > > Looking at > > https://github.com/macports/macports-ports/blob/master/aqua/iTerm2/Portfile > > The port is already limited to 10.12 or newer… > > I do still wonder if that couldn’t be extended by using the compiler black > list port group accordingly... > > On 28 Jul 2018, at 10:05 pm, Mark Anderson <e...@emer.net> wrote: > > Turns out I'm wrong, it will run 10.10+, but will only build from source > on 10.13 due to a Xcode 9.4 requirement. > > —Mark > _______________________ > Mark E. Anderson <e...@emer.net> > > > On Sat, Jul 28, 2018 at 4:53 PM Chris Jones <jon...@hep.phy.cam.ac.uk> > wrote: > >> Hi, >> >> 10.13 only would be quite a harsh requirement, so I think limiting iTerm2 >> to only that would not be good. >> >> Do you know why exactly they are doing this ? Is it the Metal 2 >> requirement, or Xcode or something else ? Sometimes within MacPorts we can >> support OSes beyond what upstream expects, as we have things like fallback >> compilers etc., whilst upstream assumes you would only use Xcode supplied >> ones. So it really depends on what the limitation actually is. >> >> Chris >> >> On 28 Jul 2018, at 9:10 pm, Mark Anderson <e...@emer.net> wrote: >> >> The upcoming 3.2 version of iTerm2 will require 10.13 or higher to build. >> The upside is Metal 2 rendering is being working on. I'm wondering if we >> want to keep older versions based on older macOSes or just say, hey, >> upstream only supports 10.XX at the latest and so that's what we support. >> >> —Mark >> _______________________ >> Mark E. Anderson <e...@emer.net> >> >> > -- Sent from Gmail Mobile on iPhone
