Skip to content

Commit

Permalink
Use clobber before generating gemspec, and ensure clobber runs clean
Browse files Browse the repository at this point in the history
  • Loading branch information
raggi committed Jan 27, 2009
1 parent 488cfac commit 5394f05
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 2 deletions.
4 changes: 3 additions & 1 deletion Rakefile
Original file line number Diff line number Diff line change
Expand Up @@ -164,6 +164,8 @@ namespace :java do
end
end

task :gemspec => :clean do
task :gemspec => :clobber do
open("eventmachine.gemspec", 'w') { |f| f.write Spec.to_ruby }
end

task :clobber => :clean
2 changes: 1 addition & 1 deletion eventmachine.gemspec
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Gem::Specification.new do |s|

s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
s.authors = ["Francis Cianfrocca"]
s.date = %q{2008-12-08}
s.date = %q{2009-01-27}
s.description = %q{EventMachine implements a fast, single-threaded engine for arbitrary network communications. It's extremely easy to use in Ruby. EventMachine wraps all interactions with IP sockets, allowing programs to concentrate on the implementation of network protocols. It can be used to create both network servers and clients. To create a server or client, a Ruby program only needs to specify the IP address and port, and provide a Module that implements the communications protocol. Implementations of several standard network protocols are provided with the package, primarily to serve as examples. The real goal of EventMachine is to enable programs to easily interface with other programs using TCP/IP, especially if custom protocols are required.}
s.email = %q{[email protected]}
s.extensions = ["Rakefile"]
Expand Down

0 comments on commit 5394f05

Please sign in to comment.