From a03120868f1e7f2022db70046e92ffa8e197cd48 Mon Sep 17 00:00:00 2001
From: Jack Nagel
Date: Mon, 19 Aug 2013 12:33:00 -0500
Subject: No longer call ENV.userpaths! in requirements

Instead we use which with a custom PATH.
---
 Library/Homebrew/test/test_requirement.rb | 4 ----
 1 file changed, 4 deletions(-)

(limited to 'Library/Homebrew/test')

diff --git a/Library/Homebrew/test/test_requirement.rb b/Library/Homebrew/test/test_requirement.rb
index a2e50126e..cba27d788 100644
--- a/Library/Homebrew/test/test_requirement.rb
+++ b/Library/Homebrew/test/test_requirement.rb
@@ -50,12 +50,10 @@ class RequirementTests < Test::Unit::TestCase
 
   def test_satisfy_sets_up_build_env_by_default
     req = Class.new(Requirement) do
-      env :userpaths
       satisfy { true }
     end.new
 
     ENV.expects(:with_build_environment).yields.returns(true)
-    ENV.expects(:userpaths!)
 
     assert req.satisfied?
   end
@@ -66,7 +64,6 @@ class RequirementTests < Test::Unit::TestCase
     end.new
 
     ENV.expects(:with_build_environment).never
-    ENV.expects(:userpaths!).never
 
     assert req.satisfied?
   end
@@ -78,7 +75,6 @@ class RequirementTests < Test::Unit::TestCase
     end.new
 
     ENV.expects(:with_build_environment).yields.returns(which_path)
-    ENV.expects(:userpaths!)
     ENV.expects(:append).with("PATH", which_path.parent, ":")
 
     req.satisfied?
-- 
cgit v1.2.3