dev-lang/ruby-1.9.3_p0 hit the tree on the last month and 1.9.3_rc1 was removed, but the prefix tree keeps 1.9.3_rc1, so I request update. I ecopied 1.9.3_p0 ebuild and copy & paste epatch lines and as such from 1.9.3_rc1 ebuild. It compiles and seems to work fine.
Created attachment 299497 [details] ruby-1.9.3_p0.ebuild
On a sidenote: I'm planning to make ruby-1.9 the only Ruby for Prefix. Would that hurt you? I'm trying to avoid the multiple Ruby mess somewhat, like we did with Python for now.
(In reply to comment #1) > Created attachment 299497 [details] > ruby-1.9.3_p0.ebuild You didn't attach a diff, so I'll stick to what eupdate has produced. Let me know if that seems not to be enough.
(In reply to comment #3) > You didn't attach a diff, so I'll stick to what eupdate has produced. Let me > know if that seems not to be enough. Let me ask you for future reference, which is better diff against 1.9.3_rc1 in prefix or 1.9.3_p0 ecopied?
hmmm, I actually don't know for this case. I'd like to know if there'd be any changes to be applied on top of the changes we already have for the latest version in the Prefix tree. eupdate applies those changes to the new ebuild. They can fail, or be no longer correct. I guess diffs/ebuilds make no sense unless you run eupdate yourself.
Ah, I misunderstood what you mean by "diff". You mean an extra diff (newly applied patch or something like that) other than what has applied to 1.9.3_rc1 in the prefix tree. And, no, there isn't such a new diff. Thank you.
