namo.rb 0.32.0 → 0.32.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 394855a4344fa3257333f89bcf0422fb7916d7e0fc517c1d5afcb9f19f7a72f4
-  data.tar.gz: 9efd44d4d29889d11631f0cb7d0a0669e2614cb6b667ce5e8abaf65cb652785a
+  metadata.gz: 2cdcd36cc0d3b94a3d75d935ec816993f2b11946b53934f93225ec24f38b9567
+  data.tar.gz: 3f6359e0309eadfe76a206e4324918567b3b097704dba6a502d1e20eacd36e6f
 SHA512:
-  metadata.gz: 0a49de0c3b6a29e5a44151065038c4b63c6645fcffca299a6b7a3efa93ee8fb27ead37eb387373a7f0c211bc53fe5925b675aabf45e14fb0595de9e6693a00ef
-  data.tar.gz: 2241f0e878f16f6dfd32a97b91645212c0b85c3e75f53c0fb3491c270a62239b402926f862fe908a1648a518bf29a3727476559dbc1ffecdf6655a6d72949b28
+  metadata.gz: 8218b30ec72a118656fcadd27af5a9213b2785d62642712a7c5bcc5cddc4195c01983a0477326a582d4657fe7f1c3b3a4842534121407d53a2183de41b661f58
+  data.tar.gz: 2ed7ed7d9ca94c3cba1c878c56c4319cad59c04e2d1d7f50f82e78174bbc2cb3c8a826098d3e3fb509b7584b8efba2471b942b145390b1d6c0d868b5545ce866

data/CHANGELOG

@@ -1,5 +1,27 @@
 # CHANGELOG
 
+## 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.
+2. ~ install.sh: the file is chosen by the login shell rather than by which file exists, a stock macOS account running zsh and possibly carrying a .bashrc which nothing reads. The directory comes from gem's own EXECUTABLE DIRECTORY rather than from gemdir with bin appended.
+3. ~ install.sh: writing to a shell configuration outlives an uninstall, so it is asked for as Homebrew is — -y answers in advance, no terminal answers no, and a refusal prints the line to add by hand.
+4. ~ install.sh: + apt-get, dnf, pacman and zypper alongside Homebrew and MacPorts, so the script reaches a Ruby on Linux rather than offering to install Homebrew on a machine which has apt. + install_with_sudo, every package manager but Homebrew installing as root, so the password is asked for by name rather than arriving unannounced.
+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.
+2. ~ install.sh: + agreed, + parse_arguments, + usage, and install_homebrew is reached only where Ruby is missing and neither Homebrew nor MacPorts is present — a package manager already installed being used before one is installed, so a MacPorts machine is never asked about Homebrew. Homebrew is used where it is already installed, and installed only on a yes — -y answers in advance, and a script piped into a shell, having nobody able to refuse, is taken to have refused. Where Ruby is missing and Homebrew is declined, + ruby_routes names the ways to get Ruby — Homebrew as the command it is, MacPorts and ruby-install as pages, and a distribution's own package manager on Linux — rather than reporting only that no package manager was found.
+3. ~ install.sh: + report_path. gem puts the command in its own directory, which is on the PATH on some machines and not on others; where it is not, the directory is named rather than somebody's shell configuration being written to.
+4. ~ README.md: + the one-line install, for a machine with neither Ruby nor the gem.
+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.

data/README.md

@@ -18,6 +18,12 @@ Or in your Gemfile:
 gem 'namo'
 ```
 
+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; `-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)"
+```
+
 ## Usage
 
 Create a Namo instance from an array of hashes:

data/bin/namo

@@ -1,9 +1,6 @@
 #!/usr/bin/env ruby
 # namo
 
-# 20260827
-# 0.0.0
-
 # Description: Install the gems Namo's own scripts want, and hand you a prompt
 # with Namo loaded.
 #

data/lib/Namo/VERSION.rb

@@ -2,5 +2,5 @@
 # Namo::VERSION
 
 class Namo
-  VERSION = '0.32.0'
+  VERSION = '0.32.2'
 end

data/test/namo_command_test.rb

@@ -29,17 +29,39 @@ describe 'bin/namo' do
     _(output).must_match(/measurand is already installed!/)
   end
 
-  # install.sh is the half a Ruby script cannot do — Homebrew, and the Ruby the
-  # script would be running on.  Its syntax is asserted and its body is not run:
-  # a test which executed it on a machine lacking Homebrew would install Homebrew.
-  it "has a shell bootstrap which parses, and which hands over to this" do
+  # install.sh is the part a Ruby script cannot do — the Ruby the script would be
+  # running on, and the gem which carries the command it hands over to.  Its
+  # syntax is asserted and its body is not run: a test which executed it on a
+  # machine without Ruby would install Ruby.
+  #
+  # It hands over by name rather than by path, which is what lets it run piped
+  # from curl — an assertion that it finds nothing by SCRIPT_DIR.
+  #
+  # It installs Homebrew only through `agreed`, which answers no unless -y was
+  # given or somebody is there to say yes.  What is asserted is that the curl of
+  # Homebrew's installer sits behind that gate: an unguarded call is the failure
+  # this is written against.
+  it "has a shell bootstrap which parses, hands over by name, and gates the one install it forces" do
     root = File.expand_path('..', __dir__)
     system("sh -n #{File.join(root, 'install.sh')}")
     _($?.success?).must_equal true
     body = File.read(File.join(root, 'install.sh'))
-    _(body).must_match(/install_homebrew/)
     _(body).must_match(/install_ruby/)
-    _(body).must_match(%r{bin/namo" setup})
+    _(body).must_match(/install_namo/)
+    %w{brew port apt-get dnf pacman zypper}.each do |manager|
+      _(body).must_match(/command -v #{manager}/)
+    end
+    _(body).must_match(/ruby_routes/)
+    _(body).must_match(/namo setup/)
+    _(body).wont_match(/SCRIPT_DIR/)
+    _(body).must_match(/elif agreed .*Install Homebrew\?.*; then\n\s+\/bin\/bash -c/)
+  end
+
+  it "declines to install anything where nothing can answer" do
+    root = File.expand_path('..', __dir__)
+    output = IO.popen([File.join(root, 'install.sh'), '--help'], chdir: root, err: [:child, :out]){|io| io.read}
+    _($?.success?).must_equal true
+    _(output).must_match(/-y, --yes/)
   end
 
   it "refuses a subcommand it does not have" do

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: namo.rb
 version: !ruby/object:Gem::Version
-  version: 0.32.0
+  version: 0.32.2
 platform: ruby
 authors:
 - thoran