namo 0.32.3 → 0.32.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1cd9dd8978eec2325228fe1c867977bb3a7d3392d97884da2cd92b497f7defd3
-  data.tar.gz: 71c01853d939dfecfb060e796b16ee8f29e050e2509657a68078f136f752299b
+  metadata.gz: fdd20fc3b0502a069ad6bf5781b183a00e1955b6b204e76a0c14551d54a7ea28
+  data.tar.gz: 6963897982afa093c48cde988071fa7bbc0c756cbf46e05ebd776ca695ed1008
 SHA512:
-  metadata.gz: 9c8f2926ab8e9f94c06a72873c0b20d65754fc1bc5a08f76aeac791bcbb24b12c8909a89d62d7a89df313115f575821eea707ee7836df2d4fe0e682ea9794efc
-  data.tar.gz: 9cea051b58185b3ba6d64d737d1d2da6f72378d628cfd7fe196e80f82619cc5ccfcfc06af02ba3400500d45b62dc85e6c51ae92e4f48e2a2570491fb6328a40b
+  metadata.gz: f9eb25cbc7db9c7af7f9f12e88be7893c972cdd4f76a3d4bf5133a6423ea41cbf27378d9a4e9e890dc09a2c38e73b1b76e4cd7218dcd08bba6bed0d49a0f440c
+  data.tar.gz: 1683cd38dfaf86011f61f2d527ba05c15c2c79eaec8cc65d4e40bd02287bca3ff80d0ebd8f8d5f91f3e5f2b4ffcb7077958a5c50af42b39db6aa05f853873f87

data/CHANGELOG

@@ -2,6 +2,15 @@
 
 ## 20260828
 
+0.32.4: ~ README.md: + Console, the command the gem has shipped since 0.32.0 going unmentioned until now.
+
+1. ~ README.md: + Console. `namo console` and `namo setup` had appeared nowhere: the gem gained an executable at 0.32.0 and the README named install.sh once, in the curl line, and the command not at all. Someone taking `gem install namo`, the first line of Installation, arrived at the library without learning that the console existed.
+2. ~ README.md: + the clone route, `git clone` and ./install.sh, which is the route the adjacent-bin/namo handover of 0.32.3 was written for and the one route no line described.
+3. ~ README.md: `gem install` and the Gemfile line say what they leave undone — the command is on the PATH only where gem's own directory is, which Homebrew's Ruby is the case against, and measurand arrives by `namo setup` rather than with the gem, a gemspec having no way to name a companion which is optional.
+4. ~ CHANGELOG: the 20260828 releases gather under one heading, as 20260824 and 20260826 gather theirs. Four releases in a day had taken a heading each.
+5. ~ Namo::VERSION: /0.32.3/0.32.4/
+
+
 0.32.3: ~ install.sh: + ruby-install, for a machine with no package manager at all; the handover is to a clone's own bin/namo where the script was run from one.
 
 1. ~ install.sh: + install_ruby_install, + ruby_from_ruby_install. Where no package manager is found and Homebrew is declined, ruby-install is offered — fetched from its latest release rather than a pinned version, built with make as root, and used to build Ruby. It is the last thing tried and the only route here which builds Ruby rather than fetching it.
@@ -13,8 +22,6 @@
 7. ~ Namo::VERSION: /0.32.2/0.32.3/
 
 
-## 20260828
-
 0.32.2: ~ install.sh: the one command ends with namo runnable from anywhere.
 
 1. ~ install.sh: + add_to_path, + gem_bin_directory, + shell_configuration_file. gem puts the command in a directory which is on the PATH on some machines and not on others — Homebrew's ruby puts it somewhere which is not — so the run ended by naming the directory and stopping. It now offers to add it to the shell's configuration file, and adds it to the PATH of the run itself so that `namo setup` happens rather than being left as a further instruction.
@@ -24,8 +31,6 @@
 5. ~ Namo::VERSION: /0.32.1/0.32.2/
 
 
-## 20260828
-
 0.32.1: ~ install.sh: it runs the same piped from curl as from a clone, and forces no package manager; ~ README.md: + the one-line install.
 
 1. ~ install.sh: the handover is to `namo setup` on the PATH rather than to bin/namo beside the script. It had found bin/namo by its own path, so piped from curl it looked in the working directory and failed there. It now finds nothing by its path and so runs from anywhere. The check is for the namo command rather than for the gem, that being what the next step needs: an older namo installs no executable.
@@ -35,8 +40,6 @@
 5. ~ Namo::VERSION: /0.32.0/0.32.1/
 
 
-## 20260828
-
 0.32.0: + bin/namo, the gem's first executable, and the gems it installs.
 
 1. + bin/namo: a setup subcommand which installs the gems Namo's scripts want — Namo itself, so that a clone leaves require 'namo' working, and measurand, which the demo's uncertainty section does without when it is missing — and a console subcommand which is bin/console. Each step asks first and says so when there is nothing to do.

data/README.md

@@ -18,12 +18,42 @@ Or in your Gemfile:
 gem 'namo'
 ```
 
+Either brings the `namo` command with it, where the directory gem installs commands into is one your PATH reaches — it is on a Ruby from ruby-install or rbenv, and is not on Homebrew's. `namo setup` then adds measurand, which the uncertainty examples want and which nothing else does.
+
+Or from a clone, which wants none of it installed first:
+
+```
+git clone https://github.com/thoran/namo.git
+cd namo
+./install.sh
+```
+
 Or from nothing at all — Ruby, the gem, and the gems its scripts want, each step skipped where it is already there. Where Ruby is missing, whichever package manager is already installed supplies it — Homebrew, MacPorts, apt, dnf, pacman or zypper; where none is, you are asked before Homebrew is installed, and then before ruby-install is built from source; `-y` answers yes in advance, and a machine with nobody at the keyboard is taken to have said no. Where the gem's own directory is not on the PATH, it offers to add it to your shell's configuration, so that a new shell has `namo` in it:
 
 ```
 sh -c "$(curl -fsSL https://raw.githubusercontent.com/thoran/namo/master/install.sh)"
 ```
 
+The two which run `install.sh` end at a `namo` which runs from anywhere. The first ends at one which runs where your PATH already reaches it.
+
+## Console
+
+The gem ships one command.
+
+```
+namo console
+```
+
+An irb session with Namo loaded, for asking a question of the library without writing a file first.
+
+```
+namo setup
+```
+
+Installs the gems the scripts want — namo itself, and measurand — skipping whichever is already there and naming each and its version either way. `install.sh` runs it as the last of its own work, so it is here for a gem which arrived by `gem install`, and for adding measurand to an installation which went without it.
+
+`namo` alone prints the usage, as `namo --help` does.
+
 ## Usage
 
 Create a Namo instance from an array of hashes:

data/lib/Namo/VERSION.rb

@@ -2,5 +2,5 @@
 # Namo::VERSION
 
 class Namo
-  VERSION = '0.32.3'
+  VERSION = '0.32.4'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: namo
 version: !ruby/object:Gem::Version
-  version: 0.32.3
+  version: 0.32.4
 platform: ruby
 authors:
 - thoran