bluepill 0.0.40 → 0.0.42

data/VERSION

@@ -1 +1 @@
-0.0.40
+0.0.42

data/bin/bluepill

@@ -28,7 +28,7 @@ OptionParser.new do |opts|
     options[:privileged] = v
   end
 
-  help = lambda do
+  help = proc do
     puts opts
     puts
     puts "Commands:"

data/bluepill.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{bluepill}
-  s.version = "0.0.40"
+  s.version = "0.0.42"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Arya Asemanfar", "Gary Tsang", "Rohith Ravi"]
-  s.date = %q{2010-08-21}
+  s.date = %q{2010-08-23}
   s.default_executable = %q{bluepill}
   s.description = %q{Bluepill keeps your daemons up while taking up as little resources as possible. After all you probably want the resources of your server to be used by whatever daemons you are running rather than the thing that's supposed to make sure they are brought back up, should they die or misbehave.}
   s.email = %q{entombedvirus@gmail.com}

data/lib/bluepill/dsl.rb

@@ -69,12 +69,18 @@ module Bluepill
         process
       end
     end
-    
     app_proxy = Class.new do
-      @@app = app
-      @@process_proxy = process_proxy
-      @@process_keys = Hash.new # because I don't want to require Set just for validations
-      @@pid_files = Hash.new
+      if RUBY_VERSION >= '1.9'
+        class_variable_set(:@@app, app)
+        class_variable_set(:@@process_proxy, process_proxy)
+        class_variable_set(:@@process_keys, Hash.new) # because I don't want to require Set just for validations
+        class_variable_set(:@@pid_files, Hash.new)
+      else
+        @@app = app
+        @@process_proxy = process_proxy
+        @@process_keys = Hash.new
+        @@pid_files = Hash.new
+      end
       attr_accessor :working_dir, :uid, :gid, :environment
       
       def validate_process(process, process_name)

data/lib/bluepill/system.rb

@@ -68,7 +68,7 @@ module Bluepill
         to_daemonize = lambda do
           # Setting end PWD env emulates bash behavior when dealing with symlinks
           Dir.chdir(ENV["PWD"] = options[:working_dir]) if options[:working_dir]
-          options[:environment].each { |key, value| ENV[key] = value } if options[:environment]
+          options[:environment].each { |key, value| ENV[key.to_s] = value.to_s } if options[:environment]
           
           redirect_io(*options.values_at(:stdin, :stdout, :stderr))
           
@@ -115,7 +115,7 @@ module Bluepill
           drop_privileges(options[:uid], options[:gid])
           
           Dir.chdir(ENV["PWD"] = options[:working_dir]) if options[:working_dir]
-          options[:environment].each { |key, value| ENV[key] = value } if options[:environment]
+          options[:environment].each { |key, value| ENV[key.to_s] = value.to_s } if options[:environment]
           
           # close unused fds so ancestors wont hang. This line is the only reason we are not
           # using something like popen3. If this fd is not closed, the .read call on the parent

data/lib/bluepill/version.rb

@@ -1,3 +1,3 @@
 module Bluepill
-  VERSION = "0.0.40"
+  VERSION = "0.0.42"
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: bluepill
 version: !ruby/object:Gem::Version 
-  hash: 79
+  hash: 75
   prerelease: false
   segments: 
   - 0
   - 0
-  - 40
-  version: 0.0.40
+  - 42
+  version: 0.0.42
 platform: ruby
 authors: 
 - Arya Asemanfar
@@ -17,7 +17,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-08-21 00:00:00 -07:00
+date: 2010-08-23 00:00:00 -07:00
 default_executable: bluepill
 dependencies: 
 - !ruby/object:Gem::Dependency