From: nobu@... Date: 2016-01-03T14:36:13+00:00 Subject: [ruby-core:72691] [Ruby trunk - Bug #11937] did_you_mean and other bundled gems are not installed by make install Issue #11937 has been updated by Nobuyoshi Nakada. Benoit Daloze wrote: > 1) Why and when should I do a `make up`? `make up` is a trigger to update via the network. Other targets would not access remote hosts, except for some necessary files (config. guess and config.sub). > And where is it documented it should be part of the the build process? (make help does not mention it for instance) Thank you, I've missed it. ---------------------------------------- Bug #11937: did_you_mean and other bundled gems are not installed by make install https://bugs.ruby-lang.org/issues/11937#change-55940 * Author: Benoit Daloze * Status: Feedback * Priority: Normal * Assignee: * ruby -v: ruby 2.4.0dev (2015-12-30 trunk 53388) [x86_64-linux] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- did_you_mean and other bundled gems are not installed when doing a regular local build: autoconf ./configure --prefix=... make install .../bin/ruby -e 'require "did_you_mean"' => LoadError `make update-gems` before `make install` will make it work, but this should be automatic (if no gems in gems/, download them and when gems/bundled_gems change fetch the new ones) or at least documented. -- https://bugs.ruby-lang.org/ Unsubscribe: