Open lewisl opened 6 years ago
Can I run brew doctor on the private Julia version?
using Homebrew; Homebrew.brew(`doctor`)
I ran the literal brew doctor and found a missing dependencies. Installed them.
Another warning occurs because the install directory for the binaries and the Homebrew cellar doesn't match what Homebrew assumes as a default: /usr/local/bin. Of course, it can't be that because the Julia Homebrew installs under dep within the package directory.
Is it possible to change the directory to ..dep/local/bin instead of ...dep/bin? This might keep Homebrew happy. Or, since this is a fork of Homebrew (which I've pointed out here and elsewhere is a misuse of your capable efforts...) change the test for the proper path to the default path used within ~/.julia/packages.
Wouldn't it be great to have these issues go away and not have to maintain this?
cc @staticfloat
I read the reasons for this special version of Homebrew: Some of the formulae in the staticfloat/juliadeps tap are specifically patched to work with Julia. Some of these patches have not (or will not) be merged back into Homebrew mainline, so we don't want to conflict with any packages the user may or may not have installed. I realize there is also a problem with paths.
I would suggest creating a special "cask" of Julia dependencies must be different than standard system packages. When this is installed, the system brew can draw from a special repository. Users will need to know to "brew cask install Julia-". Cask is meant to install binaries. Maybe it won't work; but wouldn't it be nice to work on Julia needs and new capabilities and not duplicate work that others admirably maintain? Maybe this won't work. Seems like it's worth a shot to get out of the duplication business.
It's not that there is anything wrong with doing Homebrew.jl. It's just a lot of work to keep a lot of infrastructure working and keep tracking (the incessant) changes to Homebrew. That doesn't feel like a priority. Julia is still playing catchup to a certain extent on needed packages (acknowledging impressive progress to date...). Why not focus on functionality Julia users can benefit from and not duplicate system plumbing. I realize it seems easier to go self-contained. I don't understand why the cask and special repository approach won't work. Some Python dependencies use this.
I don't have time to figure this out. I just hope it doesn't matter and I can ignore it.
Can I run brew doctor on the private Julia version?
Here is the latest problem. Sorry it is so long: