Re: port "cask" -- installing prebuilt binaries

I like the idea of a separate thing like cask, (if only in labeling) but we don't always need it/shouldn't use it exclusively. Like maybe for restrictive non-free stuff like Chrome a different mode makes sense, but with iTerm, I'm just trying to allow install on <10.15 and knowing the iTerm guy, p

Re: port "cask" -- installing prebuilt binaries

Ken Cunningham wrote: >> So, I'm looking to install iTerm2 for old systems from binary as building >> is becoming increasingly impossible - have we come to a consensus on any of >> this? >> >> —Mark >> ___ >> Mark E. Anderson >> MacPorts Trac WikiPage

Re: port "cask" -- installing prebuilt binaries

So yeah - I think that a name and separate port is a good idea. I'm also on board for the category for the 0.0001% of us that would use it. maybe category: binary and binary-PortName like we do with like py38-something —Mark ___ Mark E. Anderson MacPorts Trac WikiPage

Re: port "cask" -- installing prebuilt binaries

So, I'm looking to install iTerm2 for old systems from binary as building is becoming increasingly impossible - have we come to a consensus on any of this? —Mark ___ Mark E. Anderson https://lists.macports.org/mailman/listinfo/macports-dev>> MacPorts Trac WikiPage

Re: port "cask" -- installing prebuilt binaries

So, I'm looking to install iTerm2 for old systems from binary as building is becoming increasingly impossible - have we come to a consensus on any of this? —Mark ___ Mark E. Anderson MacPorts Trac WikiPage GitHub Profile