Looking at https://github.com/macports/macports-ports/blob/master/aqua/iTerm2/Portfile <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 <mailto:e...@emer.net>> > > > On Sat, Jul 28, 2018 at 4:53 PM Chris Jones <jon...@hep.phy.cam.ac.uk > <mailto: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 > <mailto: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 <mailto:e...@emer.net>>
smime.p7s
Description: S/MIME cryptographic signature
