bundleup 0.1.0 → 0.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 865cab477561de59cdd1c114ffa36195af57e18b
-  data.tar.gz: 71f4619cc728bcf78006f7fdb60348aa6a482756
+  metadata.gz: d61632914c5c1ca565a988a58d9afe3eb87b20b8
+  data.tar.gz: 5acef44c5c76ba56f4b45f8691440b3d5b821a8e
 SHA512:
-  metadata.gz: 3e6ebb3f257b644fa58e4b8da2644fc9a2e5c86618a18389a6812372d8c9d483e26f4bde6e9f4ae39acc11f53a54b18bb31341dc9f5d64e744b5d29a497ea390
-  data.tar.gz: 3c8247f33348a73606f922dd3de4c876226b5ccfe6c9f6f570597b0a0a99fd1167d3792c976a2b531dfeac01b49c4cf4a6bec0a1944ba7cea00ff63cfc4565de
+  metadata.gz: f760e4e30738338457bb265e70a8019e24b72495fdc0a40931598b58f4504cbdf7c557d1a87f078836ab93124d37ccdaab8cbcb9c86a5cf9add431175cd3a59e
+  data.tar.gz: 9c0fcc6014120a5bbf4a844ff58b61816a81dc19b6927d6e0e41d5188af9da329481c454f85a804925e8413c364d2e7c1feaebeebfe59507450e30e3027c9411

data/CHANGELOG.md

@@ -8,9 +8,17 @@ bundleup is in a pre-1.0 state. This means that its APIs and behavior are subjec
 
 * Your contribution here!
 
+## [0.2.0][] (2015-12-26)
+
+* Animated spinner during long-running bundler commands
+* Rather than run `bundle` in a temp directory, run within the current
+  directory, making a backup copy of Gemfile.lock. This ensures that relative
+  paths and `.bundle/config` are honored.
+
 ## 0.1.0 (2015-12-24)
 
 * Initial release
 
 [Semver]: http://semver.org
-[Unreleased]: https://github.com/mattbrictson/bundleup/compare/v0.1.0...HEAD
+[Unreleased]: https://github.com/mattbrictson/bundleup/compare/v0.2.0...HEAD
+[0.2.0]: https://github.com/mattbrictson/bundleup/compare/v0.1.0...v0.2.0

data/README.md

@@ -36,11 +36,11 @@ That’s it!
 
 ## How it works
 
-bundleup starts by making a copy of your Gemfile and Gemfile.lock into a temporary working directory. Within that directory, it runs `bundle show`, then `bundle update` and `bundle show` again to find what gems versions are being used before and after Bundler does its updating magic. (Since gems are actually being installed into your Ruby environment during these steps, the process may take a few moments to complete, especially if gems with native extensions need to be compiled.)
+bundleup starts by making a backup copy of your Gemfile.lock. Next it runs `bundle show`, then `bundle update` and `bundle show` again to find what gems versions are being used before and after Bundler does its updating magic. (Since gems are actually being installed into your Ruby environment during these steps, the process may take a few moments to complete, especially if gems with native extensions need to be compiled.)
 
-Finally, bundleup runs `bundle outdated` to see the gems that were *not* updated due to Gemfile restrictions.
+Finally, bundleup runs `bundle outdated` to see the gems that were *not* updated due to Gemfile restrictions. It then restores your original Gemfile.lock from the backup, leaving your project as it started.
 
-Since all this takes place in a temporary directory, your project’s actual Gemfile.lock is not affected. After displaying its findings, bundleup gives you the option of running `bundle update` once more against your project. This time your Gemfile.lock *will* be changed. You can skip this step if you want.
+After displaying its findings, bundleup gives you the option of running `bundle update` once more against your project. This time your Gemfile.lock *will* be changed. You can skip this step if you want.
 
 
 ## Roadmap

data/lib/bundleup/console.rb

@@ -27,11 +27,16 @@ module Bundleup
       gets =~ /^($|y)/i
     end
 
-    def progress(message)
-      print "\e[90m#{message}...\e[0m"
-      result = yield
+    def progress(message, &block)
+      print "\e[90m#{message}... \e[0m"
+      thread = Thread.new(&block)
+      thread.join(0.5)
+      %w(/ - \\ |).cycle do |char|
+        break if thread.join(0.1)
+        print "\r\e[90m#{message}... #{char} \e[0m"
+      end
       puts "\r\e[90m#{message}... OK\e[0m"
-      result
+      thread.value
     end
 
     # Given a two-dimensional Array of strings representing a table of data,

data/lib/bundleup/gemfile.rb

@@ -22,7 +22,7 @@ module Bundleup
     attr_reader :commands
 
     def load
-      in_temp_dir do
+      with_copy_of_lockfile do
         find_versions(:old)
         commands.update
         find_versions(:new)
@@ -30,14 +30,12 @@ module Bundleup
       end
     end
 
-    def in_temp_dir(&block)
-      Dir.mktmpdir do |dir|
-        FileUtils.cp("Gemfile", dir)
-        FileUtils.cp("Gemfile.lock", dir)
-        FileUtils.cp(Dir["*.gemspec"], dir) if Dir["*.gemspec"].any?
-        FileUtils.cp_r("lib", dir) if File.directory?("lib")
-        Dir.chdir(dir, &block)
-      end
+    def with_copy_of_lockfile
+      backup = ".Gemfile.lock.#{rand(1_000_000_000).to_s(36)}"
+      FileUtils.cp("Gemfile.lock", backup)
+      yield
+    ensure
+      FileUtils.mv(backup, "Gemfile.lock")
     end
 
     def find_pinned_versions

data/lib/bundleup/version.rb

@@ -1,3 +1,3 @@
 module Bundleup
-  VERSION = "0.1.0"
+  VERSION = "0.2.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: bundleup
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.2.0
 platform: ruby
 authors:
 - Matt Brictson
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2015-12-24 00:00:00.000000000 Z
+date: 2015-12-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -158,7 +158,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.4.5.1
+rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
 summary: A friendlier command-line interface for Bundler’s `update` and `outdated`