ext 0.0.7 → 0.0.8

data/Rakefile

@@ -11,7 +11,7 @@ end
 
 gem_specification = Gem::Specification.new do |specification|
   specification.name = 'ext'
-  specification.version = '0.0.7'
+  specification.version = '0.0.8'
   specification.platform = Gem::Platform::RUBY
   specification.rubyforge_project = 'ext'
   
@@ -37,7 +37,7 @@ project is checked out via "ext checkout" it knows where to fetch the
 subprojects.  
 
 There are several other useful commands, such as init, touch_emptydirs, add_all, 
-export, status.  I plan to put up a tutorial at http://nopugs.com/ext-tutorial
+export, status.  There's a tutorial at http://nopugs.com/ext-tutorial
 
 The reason I made this project is that I was frustrated by two things:
 

data/lib/externals/ext.rb

@@ -163,6 +163,7 @@ module Externals
     end
 
     def help(args, options)
+      puts "There's a tutorial available at http://nopugs.com/ext-tutorial\n\n"
       puts "#{self.class.new_opts({},{}).to_s}\n\n"
 
       puts "\nCommands that apply to the main project or the .externals file:"

data/lib/externals/scms/git_project.rb

@@ -14,7 +14,9 @@ module Externals
       puts(gitclonecmd = "git clone \"#{repository}\" #{dest}")
       puts `#{gitclonecmd}`
       if branch
-        puts `cd #{path}; git checkout --track -b #{branch} origin/#{branch}`
+        Dir.chdir path do
+          puts `git checkout --track -b #{branch} origin/#{branch}`
+        end
       end
     end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: ext
 version: !ruby/object:Gem::Version 
-  version: 0.0.7
+  version: 0.0.8
 platform: ruby
 authors: 
 - Miles Georgi
@@ -9,11 +9,11 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2008-09-04 00:00:00 -07:00
+date: 2008-09-05 00:00:00 -07:00
 default_executable: ext
 dependencies: []
 
-description: "Provides an SCM agnostic way to manage subprojects with a workflow similar  to the scm:externals feature of subversion.  It's particularly useful for rails  projects that have some plugins managed by svn and some managed by git.    For example, \"ext install git://github.com/rails/rails.git\" from within a rails  application directory will realize that this belongs in the vendor/rails folder.   It will also realize that this URL is a git repository and clone it into that  folder.    It will also add the vendor/rails folder to the ignore feature for the SCM of  the main project.  Let's say that the main project is being managed by  subversion.  In that case it adds \"rails\" to the svn:ignore property of the  vendor folder.  It also adds the URL to the .externals file so that when this  project is checked out via \"ext checkout\" it knows where to fetch the  subprojects.    There are several other useful commands, such as init, touch_emptydirs, add_all,  export, status.  I plan to put up a tutorial at http://nopugs.com/ext-tutorial  The reason I made this project is that I was frustrated by two things:  1.  In my opinion, the workflow for svn:externals is far superior to  git-submodule.    2.  Even if git-submodule was as useful as svn:externals, I would still like a  uniform way to fetch all of the subprojects regardless of the SCM used to manage  the main project."
+description: "Provides an SCM agnostic way to manage subprojects with a workflow similar  to the scm:externals feature of subversion.  It's particularly useful for rails  projects that have some plugins managed by svn and some managed by git.    For example, \"ext install git://github.com/rails/rails.git\" from within a rails  application directory will realize that this belongs in the vendor/rails folder.   It will also realize that this URL is a git repository and clone it into that  folder.    It will also add the vendor/rails folder to the ignore feature for the SCM of  the main project.  Let's say that the main project is being managed by  subversion.  In that case it adds \"rails\" to the svn:ignore property of the  vendor folder.  It also adds the URL to the .externals file so that when this  project is checked out via \"ext checkout\" it knows where to fetch the  subprojects.    There are several other useful commands, such as init, touch_emptydirs, add_all,  export, status.  There's a tutorial at http://nopugs.com/ext-tutorial  The reason I made this project is that I was frustrated by two things:  1.  In my opinion, the workflow for svn:externals is far superior to  git-submodule.    2.  Even if git-submodule was as useful as svn:externals, I would still like a  uniform way to fetch all of the subprojects regardless of the SCM used to manage  the main project."
 email: azimux@gmail.com
 executables: 
 - ext