| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(Portage version: 2.2_rc67/cvs/Linux x86_64)
|
|
|
|
|
|
| |
dependencies for tests by running them manually instead.
(Portage version: 2.2_rc67/cvs/Linux x86_64)
|
|
|
|
|
|
|
|
|
| |
customisation, all clear for upstream, while we install our own defaults in a separate file exactly as upstream intended.
This new version installs in /usr/local rather than /usr, so that whatever the user installs, it's not going to collide or mess with Portage-installed gems. Also, we no longer do any per-implementation patching, and we only special-case Ruby 1.9 for what concern the auto_gem file (instead of keeping four copies of the same identical file in files/).
Documentation is not currently building right, but tests are executed (they fail for JRuby, that is known.
Note that the -r1 version has been dropped, so for ~alpha and ~arm (which will have to re-keyword -r2) this causes a faux-downgrade to 1.3.7, but the changes in -r1 only related to Ruby 1.9 anyway.
(Portage version: 2.2_rc67/cvs/Linux x86_64)
|
|
|
|
|
|
| |
~/.gem/ruby/1.9.1 instead of ~/.gem/ruby19/1.9.1. The systemwide installation directory will follow that change eventually. Closes bug 319977.
(Portage version: 2.2_rc67/cvs/Linux x86_64)
|
|
|
|
| |
(Portage version: 2.2_rc67/cvs/Linux x86_64)
|
|
|
|
| |
(Portage version: 2.2_rc67/cvs/Linux x86_64)
|
|
|
|
|
|
| |
setting. Make use of the new ruby_rbconfig_value function from ruby-ng. Add support for multiple auto_gem.rb versions. Closes bug 307863.
(Portage version: 2.2_rc67/cvs/Linux x86_64)
|
|
|
|
| |
(Portage version: 2.2_rc67/cvs/Linux x86_64)
|
|
|
|
| |
(Portage version: 2.2_rc59/cvs/Linux x86_64)
|
|
|
|
| |
(Portage version: 2.1.6.13/cvs/Linux i686)
|
|
|
|
| |
(Portage version: 2.2_rc33/cvs/Linux x86_64)
|
|
|
|
| |
(Portage version: 2.2_rc33/cvs/Linux x86_64)
|
|
|
|
| |
(Portage version: 2.1.4.5)
|
|
|
|
| |
(Portage version: 2.1.4.5)
|
|
|
|
| |
(Portage version: 2.1.4.4)
|
|
|
|
| |
(Portage version: 2.1.4.4)
|
|
|
|
|
|
| |
stop using broken PATCHES var
(Portage version: 2.1.4.4)
|
|
|
|
| |
(Portage version: 2.1.4.4)
|
| |
|
|
|
|
| |
(Portage version: 2.1.3.19)
|
|
|
|
| |
(Portage version: 2.1.3.19)
|
|
|
|
| |
(Portage version: 2.1.3.19)
|
|
|
|
| |
(Portage version: 2.1.3.16)
|
|
|
|
|
|
| |
<henning@wh9.tu-dresden.de>, #186937
(Portage version: 2.1.3_rc8)
|
|
|
|
| |
(Portage version: 2.1.2.9)
|
|
|
|
| |
(Portage version: 2.1.2.7)
|
|
|
|
| |
(Portage version: 2.1.2.2)
|
|
|
|
| |
(Portage version: 2.1.2.2)
|
|
|
|
| |
(Portage version: 2.1.2.2)
|
|
|
|
| |
(Portage version: 2.1.2-r9)
|
|
|
|
| |
(Portage version: 2.1.2_rc4-r5)
|
|
|
|
| |
(Portage version: 2.1.2_rc4-r5)
|
|
|
|
|
| |
(Portage version: 2.1.2_rc4-r5)
(Unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.1.2_rc4-r5)
|
|
|
|
| |
(Portage version: 2.1.2_rc4-r5)
|
|
|
|
| |
(Portage version: 2.1.1)
|
|
|
|
|
|
| |
John W Higgins for suggesting the course of action.
(Portage version: 2.1.2_rc1-r2)
|
|
|
|
| |
(Portage version: 2.1.1_pre1-r5)
|
|
|
|
| |
(Portage version: 2.1_pre9-r4)
|
|
|
|
| |
(Portage version: 2.1_pre7-r5)
|
|
|
|
| |
(Portage version: 2.0.53)
|
|
|
|
|
|
| |
remove to make sure the RUBYOPT variable gets cleared if it really needs to be
(Portage version: 2.1_pre7-r2)
|
|
|
|
| |
(Portage version: 2.1_pre6-r2)
|
|
|
|
| |
(Portage version: 2.1_pre4-r1)
|
|
|
|
| |
(Portage version: 2.1_pre4-r1)
|
|
|
|
|
|
| |
loads rubygems for you
(Portage version: 2.1_pre3-r1)
|
|
|
|
| |
(Portage version: 2.1_pre3-r1)
|
|
|
|
|
|
| |
10rubygems environment file which contains RUBYOPT='-rubygems' so that s are automagically found
(Portage version: 2.0.53_rc6)
|
|
|
|
| |
(Portage version: 2.0.52-r1)
|
|
|
|
| |
(Portage version: 2.0.51.19)
|