Pistos-emerge-gem 0.3.2 → 0.3.3
Sign up to get free protection for your applications and to get access to all the features.
- data/README +8 -5
- data/lib/emerge-gem.rb +3 -3
- metadata +1 -1
data/README
CHANGED
@@ -21,11 +21,14 @@ emerge-gem will also determine gem dependencies and emerge them, too.
|
|
21
21
|
### Notes
|
22
22
|
|
23
23
|
USE emerge-gem AT YOUR OWN RISK! It is still very much alpha software as of
|
24
|
-
2009-03-01.
|
25
|
-
|
26
|
-
|
27
|
-
|
28
|
-
|
24
|
+
2009-03-01.
|
25
|
+
|
26
|
+
If you have been using the gem command to install gems outside of Portage's
|
27
|
+
control, you are advised to make use of "gem list -l" and "gem uninstall" to
|
28
|
+
check for and remove previously installed gems. This lets Portage operate with
|
29
|
+
a clean slate. After you emerge-gem, you can use "gem list -l gemname" to
|
30
|
+
verify that emerge-gem installed the gem correctly. You can emerge eix to
|
31
|
+
automate this check; emerge-gem will use eix if found.
|
29
32
|
|
30
33
|
emerge-gem works by using the Rubygems system/library to find gem sources and
|
31
34
|
dependencies, and to automatically create wrapper ebuilds for them. It then
|
data/lib/emerge-gem.rb
CHANGED
@@ -56,12 +56,12 @@ class EmergeGem
|
|
56
56
|
|
57
57
|
def check_local_gems
|
58
58
|
@gems.each do |gem|
|
59
|
-
gem_installed = system( "gem list -l #{gem} | egrep '^#{gem}'" )
|
60
|
-
eix_installed = system( 'which eix' )
|
59
|
+
gem_installed = system( "gem list -l #{gem} | egrep '^#{gem} ' > /dev/null" )
|
60
|
+
eix_installed = system( 'which eix > /dev/null' )
|
61
61
|
next if ! gem_installed || ! eix_installed
|
62
62
|
|
63
63
|
puts "(checking if #{gem} has been installed with Portage)"
|
64
|
-
package_installed = system( "eix -Ie --only-names #{gem} | egrep '#{gem}$'" )
|
64
|
+
package_installed = system( "eix -Ie --only-names #{gem} | egrep '#{gem}$' > /dev/null" )
|
65
65
|
next if package_installed
|
66
66
|
|
67
67
|
puts "#{gem} seems to be installed via gem and not Portage."
|