Consider using a package manager for MacOS in 2022

Open
#4 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
macos
Domain
tooling

Research direction

The issue names no repository files or tests. Start by reviewing the proposed Homebrew command and trialing the listed macOS installations; done means deciding whether to adopt Homebrew and documenting a supported approach after discussion.

Written by the indexing model from the issue text.

Description

enhancement

As we aim to use a package manager on Windows next year (#77), we should also consider using one for macOS (as was also pointed out to us on twitter). I think https://brew.sh/ is the only reasonable alternative as far as I understand and then the install could looks something like:

brew cask install basictex docker google-chrome lastpass postgres r rstudio slack visual-studio-code xquartz

I have a similar hesitation to this as what I had to changing to WSL this year, which that I would like one of us to be using this approach before recommending it to students, so that we're familiar with the shortcomings and advantages beyond having myself spending just a few weeks trying out the installations.

So if we think using a package manager for macOS is worthwhile, I would ask someone to champion this and use that approach themselves, probably a long term staff member such as @ttimbers @mgelbart or @kvarada. This is not urgent but I will add it to next meeting, just for a quick discussion and bring it to people's attention.

Dominant language
HTML
Stars
0
Forks
1
Avg merge
7h 32m
Merged PRs (30d)
3

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 UBC-MDS/UBC-MDS.github.io

All issues in UBC-MDS/UBC-MDS.github.io

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.