rb ports need revbump

[ryandesign (Ryan Carsten Schmidt)]

Following the changes made to the ruby-1.0 portgroup in March 2013, which added a ruby version number suffix to installed programs, all ports using the portgroup—at least those that install programs in bin—need a revbump so that they get rebuilt with those new settings. Revbumping all these ports is essential, because otherwise users installing from binaries (and those who already had the ports installed before you made these changes) will have the old program names while users building from source will have the new program names, causing havoc for other ports trying to use those ruby ports (one example: #39247).

[gjasny@…]

Cc Me!

[cooljeanius (Eric Gallager)]

Cc Me!

[cooljeanius (Eric Gallager)]

(one example: #39247).

Also: #39043

[ryandesign (Ryan Carsten Schmidt)]

Replying to egall@…:

Also: #39043

Thanks: I knew I had commented on this before but couldn't find it.

[cooljeanius (Eric Gallager)]

Replying to ryandesign@…:

Replying to egall@…:

Also: #39043

Thanks: I knew I had commented on this before but couldn't find it.

You're welcome. :-)

(I had an easier time remembering, of course, since it was a ticket I had opened myself...)

[cooljeanius (Eric Gallager)]

This should be fixed as of r106535

[ryandesign (Ryan Carsten Schmidt)]

Not entirely. For example, rb19-ronn has not yet been revbumped.

[jmroot (Joshua Root)]

And rb-rbot.

​https://lists.macosforge.org/pipermail/macports-dev/2013-March/022315.html

[gjasny@…]

Seems this ticket got stalled. Any news here?

[jmroot (Joshua Root)]

This is worse than I thought. Gems that use rake won't build unless you specify rake=rake-1.8 in the environment, since otherwise it uses the default_exec_format, which comes from ruby, and tries running rake1.8 which doesn't exist.

[kimuraw (kimura wataru)]

pass rake path via "rake" environment

[kimuraw (kimura wataru)]

I wrote a patch against group/ruby-1.0.tcl.

1. add an option "ruby.rake", means fullpath to "rake" command. such as "ruby.bin" or "ruby.gem".
2. set destroot.env rake=${ruby.rake}

DEBUG: Environment: CPATH='/opt/local/include' CC_PRINT_OPTIONS_FILE=...
rake='/opt/local/libexec/ruby1.8/rake'

DEBUG: Environment: CPATH='/opt/local/include' CC_PRINT_OPTIONS_FILE=...
rake='/opt/local/bin/rake1.9'

3. ruby-1.8 gem ports requires rb-rake as depends_build

% port info --depends rb-rcov
depends_build: port:rb-rake    # <= added by ruby.setup gem from portgroup ruby
depends_run: 
depends_fetch: 
depends_lib: port:ruby, port:rb-rubygems
depends_extract:
% port info --depends rb-rake
depends_build:                 # <= rb-rake does not require rake
depends_run: 
depends_fetch: 
depends_lib: port:ruby, port:rb-rubygems
depends_extract: 

% port info --depends rb19-rcov
depends_build: 
depends_run: 
depends_fetch: 
depends_lib: port:ruby19
depends_extract: 

how about this?

[jmroot (Joshua Root)]

Do all gems need a rake dependency?

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign@…:

Not entirely. For example, rb19-ronn has not yet been revbumped.

rb19-ronn was revbumped in r115099.

[mojca (Mojca Miklavec)]

Cc Me!