Commit graph

12 commits

Author SHA1 Message Date
Peter Hoeg e9a70ccfe9 bundler: 1.15.1 -> 1.15.3 2017-07-30 16:57:59 +08:00
Peter Hoeg b8297ff08a bundler: 1.15.0 -> 1.15.1 2017-06-21 15:29:05 +08:00
Peter Hoeg 0cbcb95e14 bundler: 1.14.6 -> 1.15.0 2017-05-31 23:26:10 +08:00
Andrzej Trzaska 376d960034 bundler: 1.14.4 -> 1.14.6 (#23930) 2017-03-15 20:34:35 +00:00
Peter Hoeg facb2c0483 bundler: 1.14.3 -> 1.14.4 2017-02-17 22:48:39 +08:00
Peter Hoeg d1b8b0dd52 bundler: 1.13.7 -> 1.14.3 (#22260) 2017-01-29 22:42:17 +00:00
Ryan Mulligan 605ec66342 bundler: 1.13.6 -> 1.13.7 2017-01-09 10:13:38 -08:00
Peter Hoeg cd11efb651 bundler: 1.13.1 -> 1.13.6 2016-10-24 23:17:23 +08:00
Peter Hoeg 73e4f644d0 bundler: 1.12.5 -> 1.13.1 2016-09-20 15:55:19 +08:00
zimbatm 6ae57b1b63 bundler: fix usage on nested call
The combination of bundler 1.12.5 and rubygems 1.6.2 doesn't play well
at all when trying to run gems such as foreman where bundler is used to
run bundler.

Just upgrading to the latest bundler rc doesn't fix it and changing rubygems causes a massive rebuild.

Issues:

- https://github.com/bundler/bundler/issues/4402
- https://github.com/bundler/bundler/issues/4576
- https://github.com/bundler/bundler/issues/4602
- https://github.com/docker-library/ruby/issues/73

This PR patches bundler to work around the issue as highlighted here and
unbreaks everything for me:

https://github.com/bundler/bundler/issues/4602#issuecomment-233619696
2016-08-29 17:03:12 +01:00
zimbatm 3086250ceb bundler: 1.11.2 -> 1.12.5 2016-06-12 13:35:15 +01:00
zimbatm 5a64bc44ea move all ruby modules to development/ruby-modules 2016-03-19 22:06:26 +00:00
Renamed from pkgs/development/interpreters/ruby/bundler.nix (Browse further)