beet 0.6.5 → 0.6.6

data/TODO

@@ -9,9 +9,11 @@
 * figure out if its worth it to use similar step definitions as done in Jeweler for gems that generate stuff
 and want to verify things worked correctly
 
-* write some recipes for browsercms
-
-* work on ubuntu install ideas
-
 * create a "if gem_exists?('browsercms')" type method
+  * perhaps repurpose the search_for_rails_2 method to search for any installed gem
+
+* add ability to set --prefix rails3 so you're not typing rails3/auth/devise, rails3/js/jquery, etc, just
+  beet -g foo --prefix rails3 -r auth/devise, js/jquery
+  * in fact, maybe make a .beetrc file where you can set a prefix permanently. 
 
+* use aruba to test beet - http://github.com/aslakhellesoy/aruba

data/VERSION

@@ -1 +1 @@
-0.6.5
+0.6.6

data/beet.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{beet}
-  s.version = "0.6.5"
+  s.version = "0.6.6"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Jack Dempsey"]
-  s.date = %q{2010-09-06}
+  s.date = %q{2010-09-07}
   s.default_executable = %q{beet}
   s.email = %q{jack.dempsey@gmail.com}
   s.executables = ["beet"]

data/lib/beet/executor.rb

@@ -1,7 +1,11 @@
 require 'open-uri'
 require 'beet/logger'
 require 'yaml'
-require 'ruby-debug'
+begin
+  require 'ruby-debug'
+rescue LoadError
+  # not required to actually run beet
+end
 
 module Beet
   class Executor

metadata

@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
   segments: 
   - 0
   - 6
-  - 5
-  version: 0.6.5
+  - 6
+  version: 0.6.6
 platform: ruby
 authors: 
 - Jack Dempsey
@@ -14,7 +14,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-09-06 00:00:00 -04:00
+date: 2010-09-07 00:00:00 -04:00
 default_executable: beet
 dependencies: 
 - !ruby/object:Gem::Dependency