smarter_bundler 0.2.1 → 0.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 1fea8b06fe9ce3d8d5e3f234d03b5170acdb7ba6
-  data.tar.gz: fce5b75f97a00df803e40db87c42a160e27330a2
+  metadata.gz: 10f203335d8ae0d93458b567e314c4e5851b4249
+  data.tar.gz: 2e015ec0fe6553e0e6d5c343ecf50425dc4421a1
 SHA512:
-  metadata.gz: 632f22a9006cbca3cd924bcfb21ab51a11b27be7857b2aff5137757df9936e325d7e0214e3487fa9afc83e8a18d60eec46267ff4c6b57b1df177cb746831e136
-  data.tar.gz: d805dff7d1dd72600f4d6b0649476f56764663d7241578eaf03793397a4fcbebabec60eb3b877edf5b7d23b415c029b1a4c7d3022ce72ee4cbe1df5e35585b53
+  metadata.gz: 53c84d3b071458b4f8a30ee31b3c19eb23d2fbca41e8c90ddef16e39c78fa90c042319e97634161f5a2382437ae517758f1939b1ed387540d0caf3b1a5a64b80
+  data.tar.gz: e0994eb574ced2f6152a02e00a9c221c5fd86e310dc17fa4aa5fb467750b2ecb495b48dd0948b1baa14e3220461178e10b03989d15b6fcbb317da212cf93e5f2

data/README.md

@@ -16,11 +16,7 @@ Do not install it via Gemfile, as it needs to execute even if bundle can't insta
 
 Use smarter_bundle instead of the bundle command when installing or upgrading gems.
 
-If you are using it in an automated deploy, then monitor the time the deploy takes, as 
-the more fixes this program does, the longer it takes (since it reruns bundler to check the fixed Gemfile).
-A reasonable limit would be four to ten times the time it normally takes to install.
-Once you hit that limit, then check your install log and incorporate the fixes it has found into your Gemfile
-source to remove the need for it to run bundler multiple times whilst it fixes the Gemfile.
+Smarter_bundle assumes that the gem bundler complains about is the one that needs to have its version restricted, as it can not determine if its that gem or the gem/s that require it that should be adjusted.
 
 ### Cleaning up afterwards
 
@@ -29,13 +25,14 @@ After smarter_bundle has updated the Gemfile, you should examine the changes, as
 2. smarter_bundle does not backtrack and recheck earlier adjustments - this may result in a gem being restricted that is no longer needed because the gem that originally needed ended up being restricted to the point it no longer has so many prerequisites. In the Gemfile.lock you will see that the gem is not required by any other gems, nor was it a gem you directly need.
 3. smarter_bundle does not know how to handle Gemfiles that are intended to be used with multiple ruby versions, so you will need to make a Gemfile that is intended for the ruby version you are checking it with and then incorporate the changes smarter_bundle makes back into the master Gemfile manually;
 
-### Using in test scripts
-
-If for some reason you do not use Gemfile.lock in automated testing (eg when testing gems with travis-ci), and you are testing against older ruby versions, then you may wish to consider using
-smarter_bundler - instead of the test script failing, smarter_bundler will update the Gemfile on the fly. Of course you are swapping processing time for convienience,
-so you should implement a time limit and manually update your Gemfile once the tests slow down too much.
+### Using in test or deploy scripts
 
-I usually prefer to fail fast and fix it then and there rather than delay the issue, but sometimes delaying failure till later when it can be worked around is appropriate.
+If you are using it in an automated deploy (ie where you are not using Gemfile.lock),
+then monitor the time the deploy takes, as 
+the more fixes this program does, the longer it takes (since it reruns bundler to check the fixed Gemfile).
+A reasonable limit would be four to ten times the time it normally takes to install.
+Once you hit that limit, then check your install log and incorporate the fixes it has found into your Gemfile
+source to remove the need for it to run bundler multiple times whilst it fixes the Gemfile.
 
 ## Notes
 

data/lib/smarter_bundler/bundle.rb

@@ -87,7 +87,16 @@ module SmarterBundler
     end
 
     def call_bundle(bundle_args)
-      shell "bundle #{bundle_args.join(' ')} && ruby -e 'puts \"Checking gems can be loaded ...\" ; require \"rubygems\" ; require \"bundler/setup\" ; Bundler.require(:default, :development, :test, :production) ; puts \"PASSED GEM LOAD TEST\" ' "
+      require_gems_check = if File.size? 'Rakefile'
+                             'bundle exec rake environment'
+                           else
+                             "ruby -e 'puts \"Checking gems can be loaded ...\" ; " +
+                             "require \"rubygems\" ; "+
+                             "require \"bundler/setup\" ; "+
+                             "Bundler.require(:default) ; "+
+                             "puts \"PASSED GEM LOAD TEST\" ' "
+                           end
+      shell "bundle #{bundle_args.join(' ')} && #{require_gems_check}"
     end
 
     def install_failed_gem(gem, version)

data/lib/smarter_bundler/version.rb

@@ -1,3 +1,3 @@
 module SmarterBundler
-  VERSION = "0.2.1"
+  VERSION = "0.2.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: smarter_bundler
 version: !ruby/object:Gem::Version
-  version: 0.2.1
+  version: 0.2.2
 platform: ruby
 authors:
 - Ian Heggie