Website's "Getting Mosh" section: macOS requirement needs updating

Open
#60 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
52/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
html, macos
Domain
documentation

Research direction

Locate the page source for the website's "Getting Mosh" section and compare its Homebrew macOS requirement with the current Homebrew requirement cited in the issue. Update the outdated installation guidance, preserving the MacPorts information if appropriate, then verify the rendered section at https://mosh.org/#getting.

Written by the indexing model from the issue text.

Description

The "Getting Mosh" section on https://mosh.org/#getting says the Homebrew version can be installed on OS X 10.5 or later. Unfortunately, my old Mac running OS X 10.7.5 can no longer run Homebrew at all (it used to be able to, but Homebrew stopped being able to update itself and now the old client can't talk to their servers) so I don't think it's fair to say it's still possible to install on 10.5 via Homebrew. Homebrew's own site now says 10.13 is required.

I can however confirm that MacPorts is still able to install Mosh on 10.7.5 in August 2020, so I have no reason to think the requirements have changed there. So perhaps MacPorts is now a better option than Homebrew if you need to put Mosh (or other tools) on an older Mac.

(The Chrome version of Mosh also fails to install on Chromium 49, which is the last version of Chromium that will run on OS X 10.7.5. But I could install Mosh on a Debian 8 image that the old Mac has installed in Vagrant/VirtualBox, and use it by doing for example vagrant ssh -c 'mosh srcf' so that might be one alternative to MacPorts if necessary.)

It's a pity that Macs are premium pieces of hardware that can last 10 years but tend to get software support for only half that time.

Dominant language
HTML
Stars
38
Forks
46
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mobile-shell/mobile-shell.github.io

All issues in mobile-shell/mobile-shell.github.io

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.