#38359: executable name of port:ruby, "ruby" to "ruby1.8" ------------------------+-------------------------------- Reporter: kimuraw@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: | ------------------------+-------------------------------- Comment (by deesto@…): Wow, this really caught me by surprise: one day Puppet was working (on 10.6), and the next, after a `port upgrade outdated`, puppet was completely broken. Initially, I thought it was expecting a different version of ruby, or location, but a sym-link from `/opt/local/bin/ruby -> /opt/local/bin/ruby` only changed the error message and didn't fix anything; then puppet would fail with: {{{ /opt/local/bin/puppet:3:in `require': no such file to load -- puppet/util/command_line (LoadError) }}} Not until reading this thread did I realize that I also had to `port select` a specific ruby version: even though I only had one version installed (1.8), ports had automatically assigned 'none' to an active state. Then not only was the creation of the above sym-link not necessary (it's created by the port select), but Puppet worked as well. Is this change considered to be working for all OS X versions, or only > 10.6? -- Ticket URL: <https://trac.macports.org/ticket/38359#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X