mikemcquaid

5 ms·

31.
by mikemcquaid 4mo ago
I've been playing around more with GitHub Actions and found that using them to do deploys, releases and (basic) "cron jobs" are nice but not widely used. Let me know if anything here useful or you disagree with!
32.
by mikemcquaid 4mo ago
Thanks for the kind words. Glad no ire directed at us. It is very frustrating I agree.
33.
by mikemcquaid 4mo ago
No apologies needed thanks for the kind words! <3
34.
by mikemcquaid 4mo ago
This behaviour came about because, before we did that we ended up upgrading just what you wanted and breaking other packages by mistake. It’s taken a long time but we’re finally at the point where we do (pretty much) only upgrade the minima
35.
by mikemcquaid 4mo ago
I’ve never applied for a job at Apple. You’re maybe thinking of the creator mxcl’s viral tweet about not getting hired at Google. He did work at Apple for a while on SwiftPM. I also am in the “applied and didn’t get hired by Google” club wh
36.
by mikemcquaid 4mo ago
brew as-console-user may help here. We don’t support a multiuser setup so there may be some limitations but we try our best to address problems as they come up.
37.
by mikemcquaid 4mo ago
You can now trust individual files inside taps. It was not clear to all users before now that some commands (before —-eval-all, a mess this replaces) would evaluate all packages Ruby code from all taps). This cleans that up and some other s
38.
by mikemcquaid 4mo ago
We’ve complained about this to Google many times to no avail. It’s very frustrating. They are literally paid money to let people install malware on your machine. Please direct all annoyance and resentment to them (we share it).
39.
by mikemcquaid 4mo ago
Sorry, we don’t have the resources to do so. We are a team of volunteers and rely on donations to pay for our CI infrastructure. MacPorts is a better fit for older hardware.
40.
by mikemcquaid 4mo ago
Thanks for the kind words and sponsorship <3
41.
by mikemcquaid 4mo ago
This sounds like a bug. Can you file an issue?
42.
by mikemcquaid 4mo ago
I square them because both of them allow me to do lots of open source work and enjoy it. Your signing point is not accurate. It doesn’t apply to all packages, only casks in the official tap. With casks the trust model, particularly on thing
43.
by mikemcquaid 4mo ago
I would say I’ve embraced AI most heavily and I wrote this document so: yes. I review AI written code on Homebrew the same way I review code from a no avatar GitHub user with no previous contributions. The experimental and abandoned brew-rs
44.
by mikemcquaid 4mo ago
https://formulae.brew.sh/analytics/homebrew-os-arch-ci/30d/ From people who haven’t disabled analytics.
45.
by mikemcquaid 4mo ago
> We'll lose support from you guys a year before Apple! Homebrew will still work (increasingly poorly) on macOS Intel for a year after that, it just won’t be “supported” or tested in CI environments (where currently macOS Intel usua
46.
by mikemcquaid 4mo ago
Try `brew version-install` (which uses `brew extract` and `brew tap-new` under the hood)
47.
by mikemcquaid 4mo ago
You’re thinking of mxcl, the creator, not me. I also applied and failed a final stage job interview at Google (and various other places over the years) but never really bothered me that much. Ironically I think I’d probably never have start
48.
by mikemcquaid 4mo ago
Thanks :) —-no-ask, —-yes, -y or HOMEBREW_NO_ASK=1
49.
by mikemcquaid 4mo ago
Very glad to hear this, thanks for posting.
50.
by mikemcquaid 4mo ago
`brew version-install` may do what you want here.
51.
by mikemcquaid 4mo ago
Glad you've found a workflow that works for you, genuinely. For others still using Homebrew: a lot of work has gone into upgrading only when we absolutely have to and showing these upgrades to the user before we do them, including in t
52.
by mikemcquaid 4mo ago
There's a selection of ways that may or may not work for you: - `formula@version` packages - `brew version-install` (which uses `brew extract` and `brew tap-new` under the hood) - `version_file:` support in `brew bundle - `brew pyenv-s
53.
by mikemcquaid 4mo ago
Our automation or a human submitted a PR, it was built and tested in our sandboxed ephemeral CI environments, a human Homebrew maintainer reviewed the CI results and PR diff and approved it for merge which happened automatically if so. If t
54.
by mikemcquaid 4mo ago
17 in September. Thanks for all your great work at the time! Hope you’re well <3
55.
by mikemcquaid 4mo ago
Yes, exactly. The goal is you can install all official packages without needing custom postinstall/preflight/postflight blocks.
56.
by mikemcquaid 4mo ago
Yes this is intended. We skip those that seem to have already auto-updated underneath. Our code for this is not yet rock solid so please file issues for those you notice are not doing the right thing here.
57.
by mikemcquaid 4mo ago
https://docs.brew.sh/Supply-Chain-Security details how we’re handling cooldowns and why we have a very different risk profile to e.g. NPM. Also, where we package things from NPM/PyPi/RubyGems that have been subjec
58.
Show HN: Homebrew 6.0.0(brew.sh)
1481 points by mikemcquaid 4mo ago|363 comments
59.
by mikemcquaid 4mo ago
kelnos beat me to it but: because working on it is fun. I don't think most people in our industry will understand decade+ open source maintainers of large projects and that's fine. I don't understand how designers can do what
60.
by mikemcquaid 4mo ago
If I hated my users I wouldn’t work on Homebrew for 17 years. I do hate a small subset of hostile users. The selling metaphor doesn’t work. Homebrew is not sold and its license, effectively a EULA, discloses all warranties because it is not

More ›