ext 0.0.6 → 0.0.7
Sign up to get free protection for your applications and to get access to all the features.
- data/Rakefile +6 -2
- metadata +2 -3
- data/bin/ext.bat +0 -6
data/Rakefile
CHANGED
|
@@ -11,7 +11,7 @@ end
|
|
|
11
11
|
|
|
12
12
|
gem_specification = Gem::Specification.new do |specification|
|
|
13
13
|
specification.name = 'ext'
|
|
14
|
-
specification.version = '0.0.
|
|
14
|
+
specification.version = '0.0.7'
|
|
15
15
|
specification.platform = Gem::Platform::RUBY
|
|
16
16
|
specification.rubyforge_project = 'ext'
|
|
17
17
|
|
|
@@ -53,7 +53,11 @@ the main project.}
|
|
|
53
53
|
specification.homepage = "http://nopugs.com/ext-tutorial"
|
|
54
54
|
|
|
55
55
|
specification.test_files = FileList['test/test_*.rb']
|
|
56
|
-
|
|
56
|
+
|
|
57
|
+
specification.bindir = "bin"
|
|
58
|
+
specification.executables = ['ext']
|
|
59
|
+
specification.default_executable = "ext"
|
|
60
|
+
|
|
57
61
|
specification.files = ['Rakefile', 'README', 'MIT_LICENSE.txt'] +
|
|
58
62
|
FileList['lib/**/*.rb']
|
|
59
63
|
#specification.require_path = 'lib'
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: ext
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.0.
|
|
4
|
+
version: 0.0.7
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Miles Georgi
|
|
@@ -10,14 +10,13 @@ bindir: bin
|
|
|
10
10
|
cert_chain: []
|
|
11
11
|
|
|
12
12
|
date: 2008-09-04 00:00:00 -07:00
|
|
13
|
-
default_executable:
|
|
13
|
+
default_executable: ext
|
|
14
14
|
dependencies: []
|
|
15
15
|
|
|
16
16
|
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."
|
|
17
17
|
email: azimux@gmail.com
|
|
18
18
|
executables:
|
|
19
19
|
- ext
|
|
20
|
-
- ext.bat
|
|
21
20
|
extensions: []
|
|
22
21
|
|
|
23
22
|
extra_rdoc_files: []
|