iTerm2 and High Sierra 10.13.6 incompatible...

[Mark Anderson]

Yeah, open a ticket. I'll take a look. I think we stopped the autoupdate
dialog before, but it moved around on us. I need to bump to at least 3.1.7
anyway.

—Mark
_______________________
Mark E. Anderson <emer at emer.net>


On Wed, Jul 18, 2018 at 3:43 PM Richard L. Hamilton <rlhamil at smart.net>
wrote:

>
>
> > On Jul 18, 2018, at 15:20, Ryan Schmidt <ryandesign at macports.org> wrote:
> >
> >
> >
> > On Jul 18, 2018, at 14:17, Richard L. Hamilton wrote:
> >
> >> But...as soon as I tried to run it, it popped up its own updater
> telling me that 3.1.7 was available.  Now I know enough NOT to use a
> non-MacPorts updater on something installed via MacPorts, but IMO, the
> MacPorts build really should (if there's a way to do it) disable the
> built-in updater, so as not to tempt people to do the wrong thing.
> >
> > Yes; by all means file a ticket about that.
> >
>
> Hmm.  I looked at the source, and there don't appear to be any #ifdefs or
> anything like that to provide a build option to disable auto-update.  So
> the scope of that might be such that it'd be an issue for upstream,
> assuming they're interested, which they might not be, since they also
> distribute binaries themselves.
>
> A note on the port telling people not to use that, and suggesting that
> they un-check "Check for updates automatically" in the General tab of the
> iTerm2 Preferences, might be a minimalist improvement on nothing at all,
> anyway.
>
> What do you suggest?  Would the note be sufficient?  And if not, where
> should the ticket be filed, with MacPorts, or upstream?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20180718/7a7d2752/attachment.html>