From: duerst@...
Date: 2014-10-15T08:46:31+00:00
Subject: [ruby-core:65723] [ruby-trunk - Bug #10380] Make sure 'update-gems' is called in the make process

Issue #10380 has been updated by Martin D��rst.


Hiroshi SHIBATA wrote:

> It will automatically install at ```make install``` therefore, Ruby 2.2 users can use it and run their test code with default installation.

Maybe this wasn't the case earlier because of bug #10372.

Also, if it's only done at install time, this means that one has to do an installation before being able to test. Shouldn't it be the other way round? (Of course, testing after installation is also a good idea to check that the installation was successful, but it's better to also test before installation to check that one installs something that's working.)

----------------------------------------
Bug #10380: Make sure 'update-gems' is called in the make process
https://bugs.ruby-lang.org/issues/10380#change-49455

* Author: Martin D��rst
* Status: Open
* Priority: Normal
* Assignee: Hiroshi SHIBATA
* Category: build
* Target version: current: 2.2.0
* ruby -v: ruby 2.2.0dev (2014-09-27 trunk 47722) [x86_64-cygwin]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
As described among else in bug #9869, minitest was removed as a default gem.

It can be installed with
> make update-gems

but I had to do that by hand. It should be done automatically (e.g. at least for make test and so on), or there should be a warning when testing without it.

P.S.: I still don't understand why we removed all testing libraries from a default installation; getting something out of the box that is reasonably complete is an important feature of a programming language, and a testing library is a very important part of that.



-- 
https://bugs.ruby-lang.org/