The Patreon page says they receive $177 per month. That's too low for a project with such a high popularity and usage.<p>I read somewhere ( and I bet ) it's used by Google / Facebook / Apple employees.
> <i>Homebrew requires the CLT on all but the latest version of macOS (to avoid copious workarounds in formulae)</i><p>Why? What are these workarounds? The linked PR didn't explain, and as someone who's still got one machine on 10.12 I'd really rather not have to keep CLT installed as well.<p>Edit: Wow, the maintainer on that PR is a real jerk. He refused to answer a legitimate question (and locked the PR at the same time) because he thought the original (since edited) complaint of "The error message for this patch is terrible" was "rude".<p>MikeMcQuaid, if you ever read this, this sort of behavior on your part is a great argument for ditching HomeBrew.
Edit: Wow...within 20 seconds of me posting this, an update to "Command Line Tools" version 9.2 showed up in the App Store app. So, if you have this problem, check updates again.<p>Anyone else getting a warning about command line tools?<p><pre><code> $ brew doctor
</code></pre>
tells me:<p><pre><code> Warning: A newer Command Line Tools release is available.
Update them from Software Update in the App Store.
</code></pre>
Looking around, I see that there are two sets of the command line tools installed. There is a set in<p><pre><code> /Library/Devloper/CommandLineTools/usr/bin
</code></pre>
and a set in<p><pre><code> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
</code></pre>
The latter is what /usr/bin/clang invokes. The /Library/Developer set is older. The file date on clang is 2017-10-20 on that one, and 2017-11-17 on the one under XCode.app.<p>Homebrew checks the command line tools version by running "clang --version". It uses this one:<p><pre><code> /Library/Devloper/CommandLineTools/usr/bin/clang
</code></pre>
It has the /Library/Developer/CommandLineTools prefix hard coded.<p>The version I have there is 900.0.38. The version under Xcode.app is 900.0.39.2 (which is the version Homebrew wants).<p>Looking back at my Time Machine backups, I see that /Library/Developer/CommandLineTools/usr did not even have a bin directory until 2017-11-23 (it just had usr/share/man). The bin directory there, and its contents, were apparently created when I installed "Command Line Tools (macOS High Sierra Version 10.13) for Xcode" version 9.1 from the App Store on 2017-11-22. That had clang version 900.0.38. That is also the version that was under Xcode.app at the time.<p>It looks like on 2017-12-06 there was an Xcode update (version 9.2) that updated the command line tools under Xcode.app bringing the clang version to 900.0.39.2 (which is the one Homebrew wants).<p>I haven't seen any updates for the "Command Line Tools" package, so what is the correct way to get the 900.0.39.2 tools into /Library/Developer/CommandLineTools/usr/bin, where Homebrew expect to find them? Is Apple just being slow to get the update out?
<i>The first-time installation on Mac OS X 10.5 has been improved</i><p>This is just pleasant to see. Some people like/are stuck using older OSes.<p>Which Apple itself conveniently ignores (inconveniently for its developers), e.g., Xcode hacks and looking for 3rd party copies of old SDKs to be able to keep compiling for older OSes. :(
To the conversation of making it easier for enterprises to support open source projects.<p>Would it make sense to create a legal entity whose only goal would be to "sell" enterprise subscriptions to open source products and then channel all the funds to those projects, after taking a reasonable cut for administrative expenses - such as invoicing, collection, production of physical media when required and etc?<p>That would make support of open source projects fit much easier into standard enterprise procurement process.<p>Each project would define different levels of subscription with different price tags. Token licenses would be generated and physical media created and mailed out.<p>Pretty sure something like this was already discussed on HN?
does homebrew still* use Github as the store for all packages?<p>Just curious, that always seemed like a strange scenario.<p>* or am I wrong that it ever did?
The maintainer's tweet about interviewing at Google is one of my favorites:<p><a href="https://mobile.twitter.com/mxcl/status/608682016205344768?lang=en" rel="nofollow">https://mobile.twitter.com/mxcl/status/608682016205344768?la...</a>