Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#38359 closed defect (fixed)

executable name of port:ruby, "ruby" to "ruby1.8"

Reported by: kimuraw (kimura wataru) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: danielluke (Daniel J. Luke), blair (Blair Zajac), raimue (Rainer Müller), nigel@…, mp@…, deesto (John S. De Stefano Jr.)
Port:

Description (last modified by ryandesign (Ryan Schmidt))

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 \

Change History (11)

comment:1 Changed 7 years ago by danielluke (Daniel J. Luke)

You've got my OK for subversion-rubybindings.

comment:2 Changed 7 years ago by ryandesign (Ryan Schmidt)

Description: modified (diff)

comment:3 Changed 7 years ago by kimuraw (kimura wataru)

Thanks dluke! I've changed subversion-rubybindings at r103977.

comment:4 Changed 7 years ago by raimue (Rainer Müller)

vim, vim-app, MacVim: I committed the change in r103978 with a rename of +ruby to +ruby18.

comment:5 in reply to:  4 Changed 7 years ago by kimuraw (kimura wataru)

Thanks raimue!

comment:6 Changed 7 years ago by mp@…

Cc: mp@… added

Cc Me!

comment:7 Changed 7 years ago by mp@…

I can confirm that a clean puppet install (that is, on a clean machine where puppet is the first install and ruby comes as a dep) 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.

Last edited 7 years ago by mp@… (previous) (diff)

comment:8 Changed 7 years ago by kimuraw (kimura wataru)

Resolution: fixed
Status: newclosed

done at r104089 for puppet and facter. thanks, all.

comment:9 Changed 7 years ago by deesto (John S. De Stefano Jr.)

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?

comment:10 Changed 7 years ago by deesto (John S. De Stefano Jr.)

Cc: deesto@… added

Cc Me!

comment:11 Changed 7 years ago by kimuraw (kimura wataru)

fixed at r105426. "port selfupdate && port upgrade puppet" solves your problem.

I've missed revison bump at r104089.

Note: See TracTickets for help on using tickets.