Bug #11937
closeddid_you_mean and other bundled gems are not installed by make install
Description
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.
Updated by nobu (Nobuyoshi Nakada) over 8 years ago
- Status changed from Open to Feedback
Doesn't make up
do it?
Updated by Eregon (Benoit Daloze) over 8 years ago
Nobuyoshi Nakada wrote:
Doesn't
make up
do it?
I guess it would, however I think there are two problems:
-
Why and when should I do a
make up
?
And where is it documented it should be part of the the build process? (make help does not mention it for instance) -
It does currently not work for me:
$ make up
Network connection closed unexpectedly: Unable to connect to a repository at URL 'svn+ssh://svn@ci.ruby-lang.org/ruby': To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file. at /usr/share/perl5/vendor_perl/Git/SVN.pm line 712.
Makefile:465: recipe for target 'up' failed
make: *** [up] Error 1
Updated by Eregon (Benoit Daloze) over 8 years ago
About 2) it's due to #11876, so after updating the keys it seems to work.
Updated by nobu (Nobuyoshi Nakada) over 8 years ago
Benoit Daloze wrote:
- 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.
Updated by Eregon (Benoit Daloze) over 8 years ago
- Status changed from Feedback to Closed
Thanks for your comments and commits, it is clearer now :)