Lines Matching +full:ruby +full:- +full:version

1 This directory contains the Ruby extension that implements Protocol Buffers
2 functionality in Ruby.
4 The Ruby extension makes use of generated Ruby code that defines message and
5 enum types in a Ruby DSL. You may write definitions in this DSL directly, but
6 we recommend using protoc's Ruby generation support with .proto files. The
8 install protoc as well to have Ruby code generation functionality.
11 ---------------------
12 In Gemfile (Please check a version of Protocol Buffers you needed [RubyGems](https://rubygems.org/g…
14     gem 'google-protobuf'
16 Or for using this pre-packaged gem, simply install it as you would any other gem:
18     $ gem install [--prerelease] google-protobuf
21 message type descriptions directly in the Ruby DSL, you do not need it.
22 However, if you wish to generate the Ruby DSL from a `.proto` file, you will
24 main `README` file. The version of `protoc` included in the latest release
25 supports the `--ruby_out` option to generate Ruby code.
27 A simple example of using the Ruby extension follows. More extensive
28 documentation may be found in the RubyDoc comments (`call-seq` tags) in the
32 ```ruby
36 #  $ protoc --ruby_out=. my_proto_types.proto
53 ---------------------------------------
55 To build this Ruby extension, you will need:
59 * Ruby development headers
65 * The latest version of the protobuf java library (see ../java/README.md)
70 Then install the required Ruby gems:
79     $ gem install `ls pkg/google-protobuf-*.gem`
85 This gem includes the upb parsing and serialization library as a single-file
86 amalgamation. It is up-to-date with upb git commit
89 Version Number Scheme
90 ---------------------
92 We are using a version number scheme that is a hybrid of Protocol Buffers'
93 overall version number and some Ruby-specific rules. Gem does not allow
94 re-uploads of a gem with the same version number, so we add a sequence number
95 ("upload version") to the version. We also format alphabetical tags (alpha,
98 * First, we determine the prefix: a Protocol Buffers version "3.0.0-alpha-2"
101 * We then append the upload version: "3.0.0.alpha.2.0" or "3.0.0.0". If we need
102   to upload a new version of the gem to fix an issue, the version becomes
104 * If we are working on a prerelease version, we append a prerelease tag:
106   version numbers are sorted, any prerelease builds are ordered between the
107   prior version and current version.
110 [Gem::Version](http://ruby-doc.org/stdlib-2.0/libdoc/rubygems/rdoc/Gem/Version.html):