Feature #9456: Include bin/racc with ruby

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

[zzak (zzak _)]

As you can see we include executables for Rake, RDoc, ri, ERB, RubyGems, and Irb with Ruby.

We should also include Racc as an executable for Ruby.

This resolves an issue where libraries requiring Racc, and using the binary executable, must install the Racc gem in order to use bin/racc.

I'm fairly sure this change won't cause any issues, so I'd be happy to commit it.

[hsbt (Hiroshi SHIBATA)]

Who are maintain it?

[zzak (zzak _)]

• Assignee set to aamine (Minero Aoki)

As Aaron has pointed out, the binary executable is GPL.

So I'm assigning this ticket to Aoki-san as this change depends on possibly re-licensing bin/racc

[naruse (Yui NARUSE)]

Why gem is not enough?
Are there libraries which need other than ext/racc?

[zzak (zzak _)]

Why gem is not enough?

For the same reason that the gem is included in stdlib, if we can't include the full functionality of the gem then it shouldn't be inclued in stdlib.

[zzak (zzak _)]

Are there libraries which need other than ext/racc?

RDoc does, here's the initial discussion that resulted in this ticket.

[david_macmahon (David MacMahon)]

I think a distinction needs to be made between the racc executable and the racc runtime library. My understanding is that the racc executable (bin/racc) is needed to develop a racc-based parser for a given application. Anyone who wants to use the application that contains the resultant parser needs the racc runtime library, but they don't need the racc executable. Thus, including the racc runtime library in the Ruby standard library is a way to ensure that racc parsers will be usable by anyone with a basic Ruby environment. Those who want to develop racc-based parsers will need the racc executable (and a suitable grammar file) to generate the parser, but those developers are more than capable of obtaining the racc executable (e.g. by installing the racc gem) for their own development environment.

Instead of asking for bin/racc to be included in the standard library, it make more sense (IMHO) to ask whether the racc runtime could be removed from the standard library so as not to favor one parser runtime library over another one. For example, since the racc runtime is included in stdlib, why not also include the treetop runtime (if there is one) or any other "runtime" library in stdlib? Where does line of reasoning end?

On the other hand, why even have a standard library if everything can be installed gems? Where would that line of reasoning end?

My guess is that the racc runtime library has been "grandfathered in" since it has been part of stdlib for so long (since Ruby 1.6?).

Dave

On Jan 27, 2014, at 6:48 PM, [e-mail] wrote:

Issue #9456 has been updated by Zachary Scott.

Why gem is not enough?

For the same reason that the gem is included in stdlib, if we can't include the full functionality of the gem then it shouldn't be inclued in stdlib.

---

Bug #9456: Include bin/racc with ruby
https://bugs.ruby-lang.org/issues/9456#change-44648

• Author: Zachary Scott
• Status: Open
• Priority: Normal
• Assignee: Minero Aoki
• Category:
• Target version: current: 2.2.0
• ruby -v: 2.2.0dev
• Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN

---

As you can see we include executables for Rake, RDoc, ri, ERB, RubyGems, and Irb with Ruby.

We should also include Racc as an executable for Ruby.

This resolves an issue where libraries requiring Racc, and using the binary executable, must install the Racc gem in order to use bin/racc.

I'm fairly sure this change won't cause any issues, so I'd be happy to commit it.

--
http://bugs.ruby-lang.org/

[drbrain (Eric Hodel)]

RDoc needs a racc runtime to parse the RD (rdtool) documentation in the ruby sources.

[hsbt (Hiroshi SHIBATA)]

• Tracker changed from Bug to Feature
• Status changed from Open to Assigned
• Assignee changed from aamine (Minero Aoki) to hsbt (Hiroshi SHIBATA)
• Target version changed from 2.2.0 to 2.5

[hsbt (Hiroshi SHIBATA)]

• Related to Feature #5481: Gemifying Ruby standard library added

[hsbt (Hiroshi SHIBATA)]

note: https://github.com/tenderlove/racc/issues/85

[naruse (Yui NARUSE)]

• Target version deleted (2.5)

[hsbt (Hiroshi SHIBATA)]

• Related to Feature #14158: Update racc library with changes from upstream added

[hsbt (Hiroshi SHIBATA)]

I update the license of Ruby to racc upstream and picked ruby-core changes.

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

After this is merged, I'm going to merge bin/racc from upstream.

[shyouhei (Shyouhei Urabe)]

hsbt (Hiroshi SHIBATA) wrote:

I update the license of Ruby to racc upstream

How dare you can do such thing? Do you actually own the copyright?

[hsbt (Hiroshi SHIBATA)]

We resolved the issue of license on upstream. I'm going to merge bin/racc after it was fixed some of build failures: https://github.com/ruby/ruby/pull/2186

[hsbt (Hiroshi SHIBATA)]

• Status changed from Assigned to Closed

I merged bin/racc at https://github.com/ruby/ruby/compare/1a2546c...754df26.