-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OS X homebrew tap #66
Comments
Hi, thanks for your work! I will post a reference to your github repo on Best regards, Alexey BataevSoftware Engineer 17.03.2015 7:04, metacollin пишет:
|
We are preparing to pull Homebrew/legacy-homebrew#33278 into Homebrew/homebrew. Are you planning to continue to use tag version schemes like "1013141148"? Is there a "stable" tagged release we can use? |
Also, would appreciate your eyes on that PR, @metacollin, if there's subtleties we should be alert to. |
Cross reference to previous issue about git tags: #46 |
My issue with MMDDYY tags is that a March 2015 tag will sort older than a October 2014 tag. |
would suggest ISO 8601 (https://xkcd.com/1179/) or semver |
Done. Tagged as 2015-04-01 Best regards, Alexey BataevSoftware Engineer 31.03.2015 19:21, Sebastian Stenzel пишет:
|
Sorry, this is the best place I could find to put this. I've created a homebrew tap that builds the non-trunk versions of llvm, clang-omp, and compiler-rt as well as intel's runtime library and handles all the paths safely and painlessly. You can find it here: https://github.com/metacollin/homebrew-clangomp
I plan to flesh out the documentation a little with instructions on setting the needed paths in Xcode soon. For now, it provides instructions only for CLI usage.
Of course, its not a universal solution and only of interest to homebrew users.
For those who have no idea what I'm talking about, homebrew is a package manager for OS X, and a tap is a user repository. :)
Anyway, I don't know if this is of any use or interest to anyone, but I've been using it for personal use and thought I'd share just in case. Again, sorry if this is not really an appropriate place to post this, but there was no other contact information on the website.
Thanks!
The text was updated successfully, but these errors were encountered: