Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#37597 closed defect (fixed)

ruby186: should conflict with ruby

Reported by: cooljeanius (Eric Gallager) Owned by: larryv (Lawrence Velázquez)
Priority: Normal Milestone:
Component: ports Version:
Keywords: haspatch Cc:
Port: ruby186 ruby

Description

ruby186 says in its description:

    Note: this port conflicts with the ruby port, so you can have either that or this one active at one time.

But it's not actually marked as conflicting with it though.

Attachments (1)

ruby186-Portfile.diff (226 bytes) - added by cooljeanius (Eric Gallager) 12 years ago.
Patch to apply to ruby186's portfile

Download all attachments as: .zip

Change History (8)

Changed 12 years ago by cooljeanius (Eric Gallager)

Attachment: ruby186-Portfile.diff added

Patch to apply to ruby186's portfile

comment:1 Changed 12 years ago by cooljeanius (Eric Gallager)

I added a patch, can someone add the keyword "haspatch" now?

comment:2 Changed 12 years ago by larryv (Lawrence Velázquez)

Cc: kimuraw@… removed
Keywords: haspatch added
Owner: changed from macports-tickets@… to kimuraw@…
Summary: ruby186 is said to be conflicting with ruby in its "description" field, but not its "conflicts" fieldruby186: should conflict with ruby
Version: 2.1.2

comment:3 Changed 12 years ago by cooljeanius (Eric Gallager)

It's been 3 weeks... this seems like a pretty easy change to make; could someone just commit it under the "obvious fix" principle?

comment:4 Changed 12 years ago by larryv (Lawrence Velázquez)

Owner: changed from kimuraw@… to larryv@…
Status: newassigned

comment:5 Changed 12 years ago by larryv (Lawrence Velázquez)

Resolution: fixed
Status: assignedclosed

Committed in r102790. You might want to open a ticket for ruby also, which unlike ruby186 is not openmaintainer.

comment:6 Changed 12 years ago by cooljeanius (Eric Gallager)

This might actually not be necessary anymore now that there's a ruby_select port.

comment:7 in reply to:  6 Changed 12 years ago by larryv (Lawrence Velázquez)

Replying to egall@…:

This might actually not be necessary anymore now that there's a ruby_select port.

ruby186 hasn’t been updated to use ruby_select.

Note: See TracTickets for help on using tickets.