Opened 10 years ago
Closed 10 years ago
#45611 closed defect (invalid)
ruby_select needs to be updated for Yosemite
Reported by: | my@… | Owned by: | kimuraw (kimura wataru) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.2 |
Keywords: | yosemite | Cc: | |
Port: | ruby_select |
Description
I cannot switch ruby back to the yosemite pre-installed ruby program.
When I run:
$ port select --list ruby
it returns:
Available versions for ruby:
none (active) ruby21
Please fix this issue. Many thanks!
B.T.W, this seems to be a universal issue for all the *_select ports. Is there a way to fix all the *_select ports once and for all?
Change History (5)
comment:1 Changed 10 years ago by larryv (Lawrence Velázquez)
Cc: | kimuraw@… openmaintainer@… removed |
---|---|
Owner: | changed from macports-tickets@… to kimuraw@… |
Summary: | ruby_select cannot detect pre-installed ruby program → ruby_select needs to be updated for Yosemite |
comment:2 Changed 10 years ago by larryv (Lawrence Velázquez)
BTW, this doesn't affect all select ports. Just the ones that provide an option corresponding to system-provided distributions. There are select ports for software that doesn't come with OS X or Xcode.
comment:3 follow-up: 4 Changed 10 years ago by rubendibattista (Ruben Di Battista)
Switching to none, at least for gcc that is what I tried, should use the OS-installed version of the executable. Is that true for everybody?
comment:4 Changed 10 years ago by larryv (Lawrence Velázquez)
That is not what happens. Using port select
sets up symlinks in the MacPorts prefix that point to a particular installation of whatever software is in question.
For example, when you use port select --set python python34
, MacPorts creates a symlink /opt/local/bin/python
(among others) that points to MacPorts’ Python 3.4. Setting port select --set python none
deletes these symlinks.
So if a particular select group is set to “none”, the usual PATH command search applies. In your case, gcc
resolves to /usr/bin/gcc
.
comment:5 Changed 10 years ago by larryv (Lawrence Velázquez)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Turns out that the ruby
select group does not provide an option for the system Ruby, and it never has. I expect that you just need to reset your command search. Run hash -r
or open a new shell. If this does not work, email macports-users for more help.
Replying to my@…:
No. Each select port specifies the relevant executables provided by the operating system, so they have to be fixed individually.