Skip to content

Commit

Permalink
extract gem specification from Rakefile into gemspec file, making peg…
Browse files Browse the repository at this point in the history
…arus git repository usable with bundler
  • Loading branch information
rkh committed Jan 27, 2011
1 parent b86c96d commit 547c355
Show file tree
Hide file tree
Showing 2 changed files with 38 additions and 38 deletions.
39 changes: 1 addition & 38 deletions Rakefile
Expand Up @@ -29,42 +29,5 @@ namespace :spec do
task :all => [:rbx, :ruby]
end

spec = Gem::Specification.new do |s|
require File.expand_path('../lib/pegarus/version', __FILE__)

s.name = "pegarus"
s.version = Pegarus::VERSION.to_s

s.specification_version = 2 if s.respond_to? :specification_version=

s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
s.authors = ["Brian Ford"]
s.date = %q{2010-10-24}
s.email = %q{brixen@gmail.com}
s.has_rdoc = true
s.extra_rdoc_files = %w[ README LICENSE ]
s.executables = []
s.files = FileList[ '{bin,lib,spec}/**/*.{yaml,txt,rb}', 'Rakefile', *s.extra_rdoc_files ]
s.homepage = %q{http://github.com/brixen/pegarus}
s.require_paths = ["lib"]
s.rubygems_version = %q{1.3.5}
s.summary = "Pegarus is an implementation of LPEG in Ruby."
s.description = <<EOS
Pegarus is, broadly, an implementation of LPEG on Rubinius. LPEG implements a
Parsing Expression Grammar using a parsing machine rather than the Packrat
algorithm. (See "A Text Pattern-Matching Tool based on Parsing Expression
Grammars" by Roberto Ierusalimschy.)
Pegarus actually implements an abstract syntax tree (AST) for the PEG. There
are various options to execute the AST against a subject string. One option is
a simple AST-walking evaluator. A second option is an implementation of the
LPEG parsing machine. A third option is a compiler that targets Rubinius
bytecode.
EOS

s.rdoc_options << '--title' << 'Pegarus Gem' <<
'--main' << 'README' <<
'--line-numbers'
end

spec = Gem::Specification.load 'pegarus.gemspec'
Rake::GemPackageTask.new(spec){ |pkg| pkg.gem_spec = spec }
37 changes: 37 additions & 0 deletions pegarus.gemspec
@@ -0,0 +1,37 @@
Gem::Specification.new do |s|
require File.expand_path('../lib/pegarus/version', __FILE__)

s.name = "pegarus"
s.version = Pegarus::VERSION.to_s

s.specification_version = 2 if s.respond_to? :specification_version=

s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
s.authors = ["Brian Ford"]
s.date = %q{2010-10-24}
s.email = %q{brixen@gmail.com}
s.has_rdoc = true
s.extra_rdoc_files = %w[ README LICENSE ]
s.executables = []
s.files = Dir[ '{bin,lib,spec}/**/*.{yaml,txt,rb}', 'Rakefile', *s.extra_rdoc_files ]
s.homepage = %q{http://github.com/brixen/pegarus}
s.require_paths = ["lib"]
s.rubygems_version = %q{1.3.5}
s.summary = "Pegarus is an implementation of LPEG in Ruby."
s.description = <<EOS
Pegarus is, broadly, an implementation of LPEG on Rubinius. LPEG implements a
Parsing Expression Grammar using a parsing machine rather than the Packrat
algorithm. (See "A Text Pattern-Matching Tool based on Parsing Expression
Grammars" by Roberto Ierusalimschy.)
Pegarus actually implements an abstract syntax tree (AST) for the PEG. There
are various options to execute the AST against a subject string. One option is
a simple AST-walking evaluator. A second option is an implementation of the
LPEG parsing machine. A third option is a compiler that targets Rubinius
bytecode.
EOS

s.rdoc_options << '--title' << 'Pegarus Gem' <<
'--main' << 'README' <<
'--line-numbers'
end

0 comments on commit 547c355

Please sign in to comment.