<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div>Looking at<div class=""><br class=""></div><div class=""><a href="https://github.com/macports/macports-ports/blob/master/aqua/iTerm2/Portfile" class="">https://github.com/macports/macports-ports/blob/master/aqua/iTerm2/Portfile</a></div><div class=""><br class=""></div><div class="">The port is already limited to 10.12 or newer…</div><div class=""><br class=""></div><div class="">I do still wonder if that couldn’t be extended by using the compiler black list port group accordingly...</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 28 Jul 2018, at 10:05 pm, Mark Anderson <<a href="mailto:emer@emer.net" class="">emer@emer.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">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.<div class=""><br clear="all" class=""><div class=""><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature">—Mark<br class="">_______________________<br class="">Mark E. Anderson <<a href="mailto:emer@emer.net" target="_blank" class="">emer@emer.net</a>><br class=""></div></div><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Sat, Jul 28, 2018 at 4:53 PM Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk" class="">jonesc@hep.phy.cam.ac.uk</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto" class=""><div class=""></div><div class="">Hi,</div><div class=""><br class=""></div><div class="">10.13 only would be quite a harsh requirement, so I think limiting iTerm2 to only that would not be good. </div><div class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class="">Chris </div><div class=""><br class="">On 28 Jul 2018, at 9:10 pm, Mark Anderson <<a href="mailto:emer@emer.net" target="_blank" class="">emer@emer.net</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">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" class=""><div class=""><div dir="ltr" class="m_8315240540030637202gmail_signature" data-smartmail="gmail_signature">—Mark<br class="">_______________________<br class="">Mark E. Anderson <<a href="mailto:emer@emer.net" target="_blank" class="">emer@emer.net</a>><br class=""></div></div></div>
</div></blockquote></div></blockquote></div>
</div></blockquote></div><br class=""></div></body></html>