inkcpp_rb 0.1.1 → 0.1.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3b5890b2bbfe3d3c602e99799b9fd2fe650fdef4679bd42faeb6b8a7d9e08996
-  data.tar.gz: 51a71c11f3584b110133d3285f4b7a7a7f249c9ad5a6155eee5999b1748878f5
+  metadata.gz: 6df4171fdae3fb72109490becde82a3c0ddfb844313aba4dae1d4fc992047d9d
+  data.tar.gz: 31444bad672062c2517af2d36306eb120e6fa0a19eaf6ea52a7df7426f8e6bea
 SHA512:
-  metadata.gz: f4e64b70c287fc7fd8e4e79e76d10d31b318abfcedf3e27a30ebe000247a55b1fdb93599ad6a4cd7cdc40da7035c3ebf4a8b4c3ec32533e2280d7ccfaa753a6f
-  data.tar.gz: 41821d98ba8b4832325d8958e7e324d4218c77c6ef703aa64037cc5bd7028a55dff3629ed5cd5560667e7cc4791a7d0e2b1f2073cf4322fe45f87c5aaa2e052f
+  metadata.gz: 79b518042aa460fdd5d421491d0382f74f23ac16c4cddf947166428fffcd2013346b664275dfb1b356bf097aa157ac2580d7907eb846c13311d8198faef0f5c6
+  data.tar.gz: 423a32aa6d86fcb5941e3e5ba29b80e85b3664b816a479c28f66c69ea0c0c96ccb4a94bbe8ca8b5f5dcfbd19df19e4437167b2819138ed5c361611d2996aaf1b

data/CHANGELOG.md

@@ -1 +1,3 @@
 0.1.0: Initial commit
+0.1.1: Adjust directory structure to fit Ruby norms
+0.1.2: Ensure Rice included as a dependency

data/Gemfile.lock

@@ -1,7 +1,8 @@
 PATH
   remote: .
   specs:
-    inkcpp_rb (0.1.1)
+    inkcpp_rb (0.1.2)
+      rice (~> 4.3.3)
 
 GEM
   remote: https://rubygems.org/
@@ -75,7 +76,6 @@ DEPENDENCIES
   minitest (~> 5.0)
   rake (~> 13.0)
   rake-compiler (~> 1.2.8)
-  rice (~> 4.3.3)
   sorbet (~> 0.5.0)
   sorbet-runtime (~> 0.5.0)
   tapioca (~> 0.16.0)

data/README.md

@@ -1,3 +1,15 @@
-# Ink RB
+# InkCPP RB
 
 These are bindings for the InkCPP project in Ruby. They largely follow the same patterns as the official Python bindings, with a few small divergences. 
+
+Install:
+
+```
+bundle add inkcpp_rb
+```
+
+Sorbet typings are included.
+
+## WARNING
+
+This gem has largely been developed for my own purposes. I am not yet confident enough in the memory semantics between Rice and InkCPP to say that this is leak free or safe to use in any important environment. If you do use this gem, I strongly suggest you use it in situations where you are not parsing untrusted user input or anything like that. 

data/inkcpp_rb.gemspec

@@ -43,8 +43,8 @@ Gem::Specification.new do |spec|
 
   # Uncomment to register a new dependency of your gem
   # spec.add_dependency "example-gem", "~> 1.0"
+  spec.add_dependency "rice", "~> 4.3.3"
   spec.add_development_dependency "rake-compiler", "~> 1.2.8"
-  spec.add_development_dependency "rice", "~> 4.3.3"
   spec.add_development_dependency "sorbet", "~> 0.5.0"
   spec.add_development_dependency "sorbet-runtime", "~> 0.5.0"
   spec.add_development_dependency "tapioca", "~> 0.16.0"

data/lib/inkcpp_rb/version.rb

@@ -1,3 +1,3 @@
 module InkcppRb
-  VERSION = "0.1.1"
-end
+  VERSION = "0.1.2"
+end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: inkcpp_rb
 version: !ruby/object:Gem::Version
-  version: 0.1.1
+  version: 0.1.2
 platform: ruby
 authors:
 - Chris Zelenak
@@ -10,33 +10,33 @@ cert_chain: []
 date: 2025-01-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
-  name: rake-compiler
+  name: rice
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.2.8
-  type: :development
+        version: 4.3.3
+  type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 1.2.8
+        version: 4.3.3
 - !ruby/object:Gem::Dependency
-  name: rice
+  name: rake-compiler
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 4.3.3
+        version: 1.2.8
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 4.3.3
+        version: 1.2.8
 - !ruby/object:Gem::Dependency
   name: sorbet
   requirement: !ruby/object:Gem::Requirement