[#97086] [Ruby master Bug#16612] Enumerator::ArithmeticSequence#last with float range produces incorrect value — muraken@...
Issue #16612 has been updated by mrkn (Kenta Murata).
4 messages
2020/02/07
[#97307] [Ruby master Feature#16663] Add block or filtered forms of Kernel#caller to allow early bail-out — headius@...
Issue #16663 has been reported by headius (Charles Nutter).
29 messages
2020/02/28
[ruby-core:97100] [Ruby master Bug#13724] make install does not install bundled gems
From:
eregontp@...
Date:
2020-02-08 22:18:17 UTC
List:
ruby-core #97100
Issue #13724 has been updated by Eregon (Benoit Daloze).
A few years later this still caught me as a big surprise:
https://github.com/ruby/openssl/pull/319#issuecomment-583781961
Most C software is fully built/installed with `./configure && make && make install`, why should Ruby be any different?
----------------------------------------
Bug #13724: make install does not install bundled gems
https://bugs.ruby-lang.org/issues/13724#change-84205
* Author: Eregon (Benoit Daloze)
* Status: Closed
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
* ruby -v: ruby 2.5.0dev (2017-07-06 trunk 59273) [x86_64-linux]
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
I believe the usual way to build C (autoconf) software is
autoconf
./configure --prefix=...
make
make install
However, such a sequence does not download nor install bundled gems.
One needs to "make up" before "make install".
This is also not documented in "make help" nor in the README:
https://github.com/ruby/ruby#how-to-compile-and-install
As a consequence many people who build ruby from the source repository might get a ruby without the usual bundled gems (and therefore different from a release).
As an example, did_you_mean does not work without "make up":
$ ruby -e 'p [].eac'
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>