Feature #15982: Remove y2racc and racc2y

• Status: Closed
• Priority: Normal
• Assignee: hsbt (Hiroshi SHIBATA)
• Target version: -

[vo.x (Vit Ondruch)]

The y2racc and racc2y are not available upstream anymore:

https://github.com/ruby/racc/commit/2d360188e9ed474d559ad2fa9bb0636feb445ea2

I know this is development branch commit, but is it worth of shipping them in Ruby if they are going to be removed in the future?

[vo.x (Vit Ondruch)]

BTW I am asking this question, because their shebang should be updated otherwise:

https://github.com/ruby/ruby/blob/master/libexec/racc2y#L1

[hsbt (Hiroshi SHIBATA)]

• Assignee set to hsbt (Hiroshi SHIBATA)
• Status changed from Open to Assigned

[hsbt (Hiroshi SHIBATA)]

https://github.com/ruby/racc/tree/1-4-stable/bin still have them. We can remove them when releasing racc-2.0.

[vo.x (Vit Ondruch)]

Yes, the stable racc has them, but

1. They were never shipped in Ruby, so if they won't be shipped, nobody should miss them.
2. It is not clear if they outputs are useful or reliable, so why to ship them if you can't tell they are useful at all.

[jeremyevans0 (Jeremy Evans)]

• Backport deleted (2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN)
• ruby -v deleted (ruby 2.7.0dev (2019-07-03T10:29:12Z master e44c9b1147) [x86_64-linux])
• Tracker changed from Bug to Feature

[vo.x (Vit Ondruch)]

hsbt (Hiroshi SHIBATA) Would you mind to reconsider as we are getting closer to the release?

[hsbt (Hiroshi SHIBATA)]

I will try to remove it at racc-1.5 in the next year.

[hsbt (Hiroshi SHIBATA)]

https://github.com/ruby/racc/pull/123

[hsbt (Hiroshi SHIBATA)]

• Status changed from Assigned to Closed

Applied in changeset git|a6864f6d2f39bcd1ff04516591cc18d4027ab186.

---

Removed the old executables of racc

[ruby-core:93516][Feature #15982]

https://github.com/ruby/racc/pull/123