-
-
Notifications
You must be signed in to change notification settings - Fork 11.4k
subversion: install --ruby
fails if brewed ruby is present
#13272
Conversation
If there's a brew-installed ruby 1.9, `brew install subversion --ruby` will fail. Setting paths to the system ruby fixes this.
Please only include the change to Subversion in this pull request; changes to homebrew itself should be in a separate request. |
I ordered the commits so that the first one only contains the minimal changes and omits the general code improvements, so you can merge just jeffstyr/homebrew@b6c0e11 and that will skip the other changes. (The commits are showing up out-of-order here in the issue view above, but that's the first commit.) |
I understand, but it makes it hard to review pull requests when they have mixed changes in them like this. |
Understood, but at this point I think that's the easiest way forward with this pull request. (I'm not sure if it's possible to attach a new branch here, and rebasing a publicly pushed branch is considered bad form.) But let me know what you want me to do. |
Oh actually, wait, I can move the branch tip back. |
Okay done. |
You can |
Yep already taken care of. Momentary lapse there. |
We'll want to use the new MacOS::SYSTEM_RUBY const that was added today, and use the library path out of |
Ha yes, that's what was in my original commit that you had me move back (using that constant, and having it point to the full path of the system Ruby down inside |
Was the (Also I did it as |
Pinging @jacknagel - the change is on his branch; I thought it was in master but I was mistaken. |
Haven't merged it yet. |
Okay ping when you have and I'll fix this up. (See above my note about path-to-ruby-executable v. path-to-ruby-base-dir.) |
Ping -- can I take this pull request and clean it up? Don't want to wait for a CONST if this solves problems now. |
Giving me:
|
Doing this on Snow Leopard and trying to use the bindings gives me:
|
MacPorts is setting "needs_relink" to no, among other things; https://trac.macports.org/browser/trunk/dports/devel/subversion-rubybindings/Portfile |
@adamv Thoughts? |
I have been too lazy to really dig into this. |
Fails under std env, of course. |
Running
brew install subversion --ruby
will fail if there is a brew-installed ruby 1.9, because subversion requires 1.8 and it's finding the 1.9.The attached fix sets a few paths explicitly to the system ruby location, and sets a more specific ruby library version so that 1.8 will get used. This allows the install to succeed.