Project

General

Profile

Bug #10380

Make sure 'update-gems' is called in the make process

Added by duerst (Martin Dürst) almost 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Target version:
ruby -v:
ruby 2.2.0dev (2014-09-27 trunk 47722) [x86_64-cygwin]
[ruby-core:65693]

Description

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.


Related issues

Related to Ruby master - Bug #9869: Rubygems tests fail in test-allThird Party's Issuehsbt (Hiroshi SHIBATA)05/28/2014Actions

Updated by duerst (Martin Dürst) almost 6 years ago

  • Related to Bug #9869: Rubygems tests fail in test-all added

Updated by hsbt (Hiroshi SHIBATA) almost 6 years ago

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.

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

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.

Updated by duerst (Martin Dürst) almost 6 years ago

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.)

Updated by hsbt (Hiroshi SHIBATA) almost 6 years ago

  • Status changed from Open to Closed

fixed at r48558

#5

Updated by usa (Usaku NAKAMURA) over 5 years ago

  • Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN to 2.0.0: DONTNEED, 2.1: DONTNEED

Also available in: Atom PDF