<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>Hi,</div><div><br></div><div>10.13 only would be quite a harsh requirement, so I think limiting iTerm2 to only that would not be good. </div><div><br></div><div>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.</div><div><br></div><div>Chris </div><div><br>On 28 Jul 2018, at 9:10 pm, Mark Anderson <<a href="mailto:emer@emer.net">emer@emer.net</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>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.</div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">—Mark<br>_______________________<br>Mark E. Anderson <<a href="mailto:emer@emer.net" target="_blank">emer@emer.net</a>><br></div></div></div>
</div></blockquote></body></html>