https://redmine.ruby-lang.org/https://redmine.ruby-lang.org/favicon.ico?17113305112014-10-14T04:09:38ZRuby Issue Tracking SystemRuby master - Bug #10380: Make sure 'update-gems' is called in the make processhttps://redmine.ruby-lang.org/issues/10380?journal_id=494232014-10-14T04:09:38Zduerst (Martin Dürst)duerst@it.aoyama.ac.jp
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-8 priority-4 priority-default closed" href="/issues/9869">Bug #9869</a>: Rubygems tests fail in test-all</i> added</li></ul> Ruby master - Bug #10380: Make sure 'update-gems' is called in the make processhttps://redmine.ruby-lang.org/issues/10380?journal_id=494282014-10-14T11:18:13Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org
<ul></ul><blockquote>
<p>It can be installed with</p>
<blockquote>
<p>make update-gems</p>
</blockquote>
<p>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>
</blockquote>
<p>It will automatically install at <code>make install</code> therefore, Ruby 2.2 users can use it and run their test code with default installation.</p>
<blockquote>
<p>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.</p>
</blockquote> Ruby master - Bug #10380: Make sure 'update-gems' is called in the make processhttps://redmine.ruby-lang.org/issues/10380?journal_id=494552014-10-15T08:46:30Zduerst (Martin Dürst)duerst@it.aoyama.ac.jp
<ul></ul><p>Hiroshi SHIBATA wrote:</p>
<blockquote>
<p>It will automatically install at <code>make install</code> therefore, Ruby 2.2 users can use it and run their test code with default installation.</p>
</blockquote>
<p>Maybe this wasn't the case earlier because of bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Problem with relative paths in update-gems makefile rule (common.mk) (Closed)" href="https://redmine.ruby-lang.org/issues/10372">#10372</a>.</p>
<p>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.)</p> Ruby master - Bug #10380: Make sure 'update-gems' is called in the make processhttps://redmine.ruby-lang.org/issues/10380?journal_id=500982014-11-26T10:07:49Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>fixed at r48558</p> Ruby master - Bug #10380: Make sure 'update-gems' is called in the make processhttps://redmine.ruby-lang.org/issues/10380?journal_id=511272015-01-20T03:15:47Zusa (Usaku NAKAMURA)usa@garbagecollect.jp
<ul><li><strong>Backport</strong> changed from <i>2.0.0: UNKNOWN, 2.1: UNKNOWN</i> to <i>2.0.0: DONTNEED, 2.1: DONTNEED</i></li></ul>