Properly close rb-fsevent pipe after killed it

Closes #5.
This commit is contained in:
Thibaud Guillaume-Gentil 2010-10-25 21:36:04 +02:00
parent 7bae189eba
commit 5d0ec698de
3 changed files with 9 additions and 3 deletions

View File

@ -2,6 +2,12 @@
Bugs fixes:
- Avoid creating new copy of fsevent_watch every time a file is changed. (issue #5)
== 0.2.1 (Oct 24, 2010)
Bugs fixes:
- Fixes for Linux support
== 0.2.0 (Oct 21, 2010)

View File

@ -5,7 +5,7 @@ gemspec
require 'rbconfig'
if Config::CONFIG['target_os'] =~ /darwin/i
gem 'rb-fsevent', '>= 0.3.3'
gem 'rb-fsevent', '>= 0.3.4'
gem 'growl', '~> 1.0.3'
end
if Config::CONFIG['target_os'] =~ /linux/i

View File

@ -25,8 +25,8 @@ module Guard
def self.usable?
require 'rb-fsevent'
if !defined?(FSEvent::VERSION) || Gem::Version.new(FSEvent::VERSION) < Gem::Version.new('0.3.3')
UI.info "Please update rb-fsevent (>= 0.3.3)"
if !defined?(FSEvent::VERSION) || Gem::Version.new(FSEvent::VERSION) < Gem::Version.new('0.3.4')
UI.info "Please update rb-fsevent (>= 0.3.4)"
false
else
true