#38359: executable name of port:ruby, "ruby" to "ruby1.8" ------------------------+-------------------------------- Reporter: kimuraw@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Description changed by ryandesign@…: Old description:

I introduced "port select ruby" at r103918(https://trac.macports.org/changeset/103918). now, ${prefix}/bin/ruby becomes ${prefix}/bin/ruby1.8.

I found the following ports use ${prefix}/bin/ruby in Portfile. Can I change "ruby" to "ruby1.8" in these portfiles?

{{{ devel/subversion-rubybindings/Portfile 40:configure.env RUBY=${prefix}/bin/ruby

editors/MacVim/Portfile 162: configure.args-append --with-ruby-command=${prefix}/bin/ruby 167: configure.args-append --with-ruby-command=${prefix}/bin/ruby1.9

editors/vim/Portfile 968: configure.args-append --with-ruby-command=${prefix}/bin/ruby 973: configure.args-append --with-ruby-command=${prefix}/bin/ruby1.9

editors/vim-app/Portfile 987: configure.args-append --with-ruby-command=${prefix}/bin/ruby 992: configure.args-append --with-ruby-command=${prefix}/bin/ruby1.9

sysutils/facter/Portfile 36:destroot.cmd ${prefix}/bin/ruby ${worksrcpath}/install.rb \

sysutils/puppet/Portfile 35:destroot.cmd ${prefix}/bin/ruby ${worksrcpath}/install.rb \ }}}

New description: I introduced "port select ruby" at r103918. now, ${prefix}/bin/ruby becomes ${prefix}/bin/ruby1.8. I found the following ports use ${prefix}/bin/ruby in Portfile. Can I change "ruby" to "ruby1.8" in these portfiles? {{{ devel/subversion-rubybindings/Portfile 40:configure.env RUBY=${prefix}/bin/ruby editors/MacVim/Portfile 162: configure.args-append --with-ruby-command=${prefix}/bin/ruby 167: configure.args-append --with-ruby-command=${prefix}/bin/ruby1.9 editors/vim/Portfile 968: configure.args-append --with-ruby-command=${prefix}/bin/ruby 973: configure.args-append --with-ruby-command=${prefix}/bin/ruby1.9 editors/vim-app/Portfile 987: configure.args-append --with-ruby-command=${prefix}/bin/ruby 992: configure.args-append --with-ruby-command=${prefix}/bin/ruby1.9 sysutils/facter/Portfile 36:destroot.cmd ${prefix}/bin/ruby ${worksrcpath}/install.rb \ sysutils/puppet/Portfile 35:destroot.cmd ${prefix}/bin/ruby ${worksrcpath}/install.rb \ }}} -- -- Ticket URL: <https://trac.macports.org/ticket/38359#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X

#38359: executable name of port:ruby, "ruby" to "ruby1.8" ------------------------+-------------------------------- Reporter: kimuraw@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Comment (by raimue@…): vim, vim-app, MacVim: I committed the change in r103978 with a rename of +ruby to +ruby18. -- Ticket URL: <https://trac.macports.org/ticket/38359#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X

#38359: executable name of port:ruby, "ruby" to "ruby1.8" ------------------------+-------------------------------- Reporter: kimuraw@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | ------------------------+-------------------------------- Comment (by mp@…): I can confirm that a clean puppet install is currently broken unless one executes "port select ruby ruby18". Puppet seems to work well with ruby18, so please don't wait too long for approval regarding puppet/facter to save others trouble. -- Ticket URL: <https://trac.macports.org/ticket/38359#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X

#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