gemrage 0.3.2 → 0.4.0
Sign up to get free protection for your applications and to get access to all the features.
- data/Gemfile +1 -0
- data/Gemfile.lock +6 -0
- data/VERSION +1 -1
- data/gemrage.gemspec +160 -2
- data/lib/rubygems/commands/scan_command.rb +26 -7
- data/spec/spec_helper.rb +2 -1
- data/vendor/ruby/1.8/bin/launchy +19 -0
- data/vendor/ruby/1.8/bin/rake +19 -0
- data/vendor/ruby/1.8/cache/configuration-1.1.0.gem +0 -0
- data/vendor/ruby/1.8/cache/launchy-0.3.7.gem +0 -0
- data/vendor/ruby/1.8/cache/rake-0.8.7.gem +0 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/README +197 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/README.erb +69 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/Rakefile +241 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/config/a.rb +5 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/config/b.rb +19 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/config/c.rb +8 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/config/d.rb +5 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/config/e.rb +13 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/configuration.gemspec +28 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/lib/configuration.rb +199 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/samples/a.rb +11 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/samples/b.rb +11 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/samples/c.rb +11 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/samples/d.rb +14 -0
- data/vendor/ruby/1.8/gems/configuration-1.1.0/samples/e.rb +12 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/HISTORY +71 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/LICENSE +16 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/README +53 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/Rakefile +62 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/bin/launchy +12 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/gemspec.rb +41 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/lib/launchy/application.rb +178 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/lib/launchy/browser.rb +98 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/lib/launchy/command_line.rb +48 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/lib/launchy/paths.rb +53 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/lib/launchy/version.rb +17 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/lib/launchy.rb +53 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/spec/application_spec.rb +62 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/spec/browser_spec.rb +58 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/spec/launchy_spec.rb +18 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/spec/paths_spec.rb +15 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/spec/spec_helper.rb +5 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/spec/tattle-host-os.yml +427 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/spec/version_spec.rb +11 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/tasks/announce.rake +39 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/tasks/config.rb +107 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/tasks/distribution.rake +46 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/tasks/documentation.rake +32 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/tasks/rspec.rake +37 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/tasks/rubyforge.rake +52 -0
- data/vendor/ruby/1.8/gems/launchy-0.3.7/tasks/utils.rb +80 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/CHANGES +440 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/MIT-LICENSE +21 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/README +196 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/Rakefile +430 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/TODO +20 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/bin/rake +31 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/command_line_usage.rdoc +102 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/example/Rakefile1 +38 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/example/Rakefile2 +35 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/example/a.c +6 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/example/b.c +6 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/example/main.c +11 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/glossary.rdoc +51 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/jamis.rb +591 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/proto_rake.rdoc +127 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/rake.1.gz +0 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/rakefile.rdoc +534 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/rational.rdoc +151 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.4.14.rdoc +23 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.4.15.rdoc +35 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.5.0.rdoc +53 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.5.3.rdoc +78 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.5.4.rdoc +46 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.6.0.rdoc +141 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.7.0.rdoc +119 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.7.1.rdoc +59 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.7.2.rdoc +121 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.7.3.rdoc +47 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.8.0.rdoc +114 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.8.2.rdoc +165 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.8.3.rdoc +112 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.8.4.rdoc +147 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.8.5.rdoc +53 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.8.6.rdoc +55 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/doc/release_notes/rake-0.8.7.rdoc +55 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/install.rb +88 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/alt_system.rb +108 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/classic_namespace.rb +8 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/clean.rb +33 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/contrib/compositepublisher.rb +24 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/contrib/ftptools.rb +153 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/contrib/publisher.rb +75 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/contrib/rubyforgepublisher.rb +18 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/contrib/sshpublisher.rb +47 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/contrib/sys.rb +209 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/gempackagetask.rb +97 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/loaders/makefile.rb +42 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/packagetask.rb +184 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb +5 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/rdoctask.rb +209 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/ruby182_test_unit_fix.rb +23 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/runtest.rb +23 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/tasklib.rb +23 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/testtask.rb +161 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake/win32.rb +55 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/lib/rake.rb +2506 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/capture_stdout.rb +26 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/check_expansion.rb +5 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/check_no_expansion.rb +5 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/contrib/test_sys.rb +47 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/chains/Rakefile +15 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/default/Rakefile +19 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/dryrun/Rakefile +22 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/file_creation_task/Rakefile +33 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/imports/Rakefile +19 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/imports/deps.mf +1 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/multidesc/Rakefile +17 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/namespace/Rakefile +57 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/rakelib/test1.rb +3 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/rbext/rakefile.rb +3 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/sample.mf +14 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/statusreturn/Rakefile +8 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/data/unittest/Rakefile +1 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/filecreation.rb +32 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/functional.rb +15 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/in_environment.rb +30 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/rake_test_setup.rb +24 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/reqfile.rb +3 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/reqfile2.rb +3 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/session_functional.rb +339 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/shellcommand.rb +3 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_application.rb +675 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_clean.rb +14 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_definitions.rb +85 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_earlytime.rb +35 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_extension.rb +63 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_file_creation_task.rb +62 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_file_task.rb +143 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_filelist.rb +623 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_fileutils.rb +251 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_ftp.rb +59 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_invocation_chain.rb +81 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_makefile_loader.rb +26 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_multitask.rb +45 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_namespace.rb +55 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_package_task.rb +118 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_pathmap.rb +210 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_pseudo_status.rb +26 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_rake.rb +41 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_rdoc_task.rb +88 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_require.rb +35 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_rules.rb +349 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_task_arguments.rb +89 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_task_manager.rb +173 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_tasklib.rb +12 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_tasks.rb +374 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_test_task.rb +77 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_top_level_functions.rb +86 -0
- data/vendor/ruby/1.8/gems/rake-0.8.7/test/test_win32.rb +72 -0
- data/vendor/ruby/1.8/specifications/configuration-1.1.0.gemspec +27 -0
- data/vendor/ruby/1.8/specifications/launchy-0.3.7.gemspec +44 -0
- data/vendor/ruby/1.8/specifications/rake-0.8.7.gemspec +32 -0
- metadata +163 -5
@@ -0,0 +1,47 @@
|
|
1
|
+
= Rake 0.7.3 Released
|
2
|
+
|
3
|
+
Rake version 0.7.3 is a minor release that includes some refactoring to better
|
4
|
+
support custom Rake applications.
|
5
|
+
|
6
|
+
== Changes
|
7
|
+
|
8
|
+
=== New Features in Version 0.7.3
|
9
|
+
|
10
|
+
* Added the +init+ and +top_level+ methods to make the creation of custom Rake applications a bit easier. E.g.
|
11
|
+
|
12
|
+
gem 'rake', ">= 0.7.3"
|
13
|
+
require 'rake'
|
14
|
+
|
15
|
+
Rake.application.init('myrake')
|
16
|
+
|
17
|
+
task :default do
|
18
|
+
something_interesting
|
19
|
+
end
|
20
|
+
|
21
|
+
Rake.application.top_level
|
22
|
+
|
23
|
+
== What is Rake
|
24
|
+
|
25
|
+
Rake is a build tool similar to the make program in many ways. But instead of
|
26
|
+
cryptic make recipes, Rake uses standard Ruby code to declare tasks and
|
27
|
+
dependencies. You have the full power of a modern scripting language built
|
28
|
+
right into your build tool.
|
29
|
+
|
30
|
+
== Availability
|
31
|
+
|
32
|
+
The easiest way to get and install rake is via RubyGems ...
|
33
|
+
|
34
|
+
gem install rake (you may need root/admin privileges)
|
35
|
+
|
36
|
+
Otherwise, you can get it from the more traditional places:
|
37
|
+
|
38
|
+
Home Page:: http://rake.rubyforge.org/
|
39
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
40
|
+
|
41
|
+
== Thanks
|
42
|
+
|
43
|
+
As usual, it was input from users that drove a alot of these changes. The
|
44
|
+
following people either contributed patches, made suggestions or made
|
45
|
+
otherwise helpful comments. Thanks to ...
|
46
|
+
|
47
|
+
-- Jim Weirich
|
@@ -0,0 +1,114 @@
|
|
1
|
+
= Rake 0.8.0/0.8.1 Released
|
2
|
+
|
3
|
+
Rake version 0.8.0 is a new release of rake that includes serveral new
|
4
|
+
features.
|
5
|
+
|
6
|
+
== Changes
|
7
|
+
|
8
|
+
=== New Features in Version 0.8.0
|
9
|
+
|
10
|
+
* Tasks can now receive command line parameters. See the examples
|
11
|
+
below for more details.
|
12
|
+
|
13
|
+
* Comments are limited to 80 columns on output, but full comments can
|
14
|
+
be seen by using the -D parameter. (feature suggested by Jamis
|
15
|
+
Buck).
|
16
|
+
|
17
|
+
* Explicit exit(n) calls will now set the exit status to n. (patch
|
18
|
+
provided by Stephen Touset).
|
19
|
+
|
20
|
+
* Rake is now compatible with Ruby 1.9.
|
21
|
+
|
22
|
+
Version 0.8.1 is a minor update that includes additional Ruby 1.9
|
23
|
+
compatibility fixes.
|
24
|
+
|
25
|
+
== What is Rake
|
26
|
+
|
27
|
+
Rake is a build tool similar to the make program in many ways. But
|
28
|
+
instead of cryptic make recipes, Rake uses standard Ruby code to
|
29
|
+
declare tasks and dependencies. You have the full power of a modern
|
30
|
+
scripting language built right into your build tool.
|
31
|
+
|
32
|
+
== Availability
|
33
|
+
|
34
|
+
The easiest way to get and install rake is via RubyGems ...
|
35
|
+
|
36
|
+
gem install rake (you may need root/admin privileges)
|
37
|
+
|
38
|
+
Otherwise, you can get it from the more traditional places:
|
39
|
+
|
40
|
+
Home Page:: http://rake.rubyforge.org/
|
41
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
42
|
+
|
43
|
+
== Task Argument Examples
|
44
|
+
|
45
|
+
Prior to version 0.8.0, rake was only able to handle command line
|
46
|
+
arguments of the form NAME=VALUE that were passed into Rake via the
|
47
|
+
ENV hash. Many folks had asked for some kind of simple command line
|
48
|
+
arguments, perhaps using "--" to separate regular task names from
|
49
|
+
argument values on the command line. The problem is that there was no
|
50
|
+
easy way to associate positional arguments on the command line with
|
51
|
+
different tasks. Suppose both tasks :a and :b expect a command line
|
52
|
+
argument: does the first value go with :a? What if :b is run first?
|
53
|
+
Should it then get the first command line argument.
|
54
|
+
|
55
|
+
Rake 0.8.0 solves this problem by explicitly passing values directly
|
56
|
+
to the tasks that need them. For example, if I had a release task
|
57
|
+
that required a version number, I could say:
|
58
|
+
|
59
|
+
rake release[0.8.0]
|
60
|
+
|
61
|
+
And the string "0.8.0" will be passed to the :release task. Multiple
|
62
|
+
arguments can be passed by separating them with a comma, for example:
|
63
|
+
|
64
|
+
rake name[john,doe]
|
65
|
+
|
66
|
+
Just a few words of caution. The rake task name and its arguments
|
67
|
+
need to be a single command line argument to rake. This generally
|
68
|
+
means no spaces. If spaces are needed, then the entire rake +
|
69
|
+
argument string should be quoted. Something like this:
|
70
|
+
|
71
|
+
rake "name[billy bob, smith]"
|
72
|
+
|
73
|
+
(Quoting rules vary between operating systems and shells, so make sure
|
74
|
+
you consult the proper docs for your OS/shell).
|
75
|
+
|
76
|
+
=== Tasks that Expect Parameters
|
77
|
+
|
78
|
+
Parameters are only given to tasks that are setup to expect them. In
|
79
|
+
order to handle named parameters, the task declaration syntax for
|
80
|
+
tasks has been extended slightly.
|
81
|
+
|
82
|
+
For example, a task that needs a first name and last name might be
|
83
|
+
declared as:
|
84
|
+
|
85
|
+
task :name, :first_name, :last_name
|
86
|
+
|
87
|
+
The first argument is still the name of the task (:name in this case).
|
88
|
+
The next to argumements are the names of the parameters expected by
|
89
|
+
:name (:first_name and :last_name in the example).
|
90
|
+
|
91
|
+
To access the values of the paramters, the block defining the task
|
92
|
+
behaviour can now accept a second parameter:
|
93
|
+
|
94
|
+
task :name, :first_name, :last_name do |t, args|
|
95
|
+
puts "First name is #{args.first_name}"
|
96
|
+
puts "Last name is #{args.last_name}"
|
97
|
+
end
|
98
|
+
|
99
|
+
The first argument of the block "t" is always bound to the current
|
100
|
+
task object. The second argument "args" is an open-struct like object
|
101
|
+
that allows access to the task arguments. Extra command line
|
102
|
+
arguments to a task are ignored. Missing command line arguments are
|
103
|
+
given the nil value.
|
104
|
+
|
105
|
+
== Thanks
|
106
|
+
|
107
|
+
As usual, it was input from users that drove a alot of these changes. The
|
108
|
+
following people either contributed patches, made suggestions or made
|
109
|
+
otherwise helpful comments. Thanks to ...
|
110
|
+
|
111
|
+
* Jamis Buck (for comment formatting suggestions)
|
112
|
+
* Stephen Touset (for exit status patch).
|
113
|
+
|
114
|
+
-- Jim Weirich
|
@@ -0,0 +1,165 @@
|
|
1
|
+
= Rake 0.8.2 Released
|
2
|
+
|
3
|
+
Rake version 0.8.2 is a new release of rake that includes a number of
|
4
|
+
new features and numerous bug fixes.
|
5
|
+
|
6
|
+
== Changes
|
7
|
+
|
8
|
+
=== New Features in Version 0.8.2
|
9
|
+
|
10
|
+
* Switched from getoptlong to optparse (patches supplied by Edwin
|
11
|
+
Pratomo).
|
12
|
+
|
13
|
+
* The -T option will now attempt to dynamically sense the size of the
|
14
|
+
terminal. The -T output will only self-truncate if the output is a
|
15
|
+
tty. However, if RAKE_COLUMNS is explicitly set, it will be honored
|
16
|
+
in any case. (Patch provided by Gavin Stark).
|
17
|
+
|
18
|
+
* The following public methods have been added to rake task objects:
|
19
|
+
|
20
|
+
* task.clear -- Clear both the prerequisites and actions of the
|
21
|
+
target rake task.
|
22
|
+
* task.clear_prerequisites -- Clear all the existing prerequisites
|
23
|
+
from the target rake task.
|
24
|
+
* task.clear_actions -- Clear all the existing actions from the
|
25
|
+
target rake task.
|
26
|
+
* task.reenable -- Re-enable a task, allowing its actions to be
|
27
|
+
executed again if the task is invoked.
|
28
|
+
|
29
|
+
* Changed RDoc test task to have no default template. This makes it
|
30
|
+
easier for the tempate to pick up the template from the environment.
|
31
|
+
|
32
|
+
* Default values for task arguments can easily be specified with the
|
33
|
+
:with_defaults method. (Idea for default argument merging supplied
|
34
|
+
by (Adam Q. Salter)
|
35
|
+
|
36
|
+
=== Bug Fixes in Version 0.8.2
|
37
|
+
|
38
|
+
* Fixed bug in package task so that it will include the subdir
|
39
|
+
directory in the package for testing. (Bug found by Adam Majer)
|
40
|
+
|
41
|
+
* Fixed filename dependency order bug in test_inspect_pending and
|
42
|
+
test_to_s_pending. (Bug found by Adam Majer)
|
43
|
+
|
44
|
+
* Fixed check for file utils options to make them immune to the
|
45
|
+
symbol/string differences. (Patch supplied by Edwin Pratomo)
|
46
|
+
|
47
|
+
* Fixed bug with rules involving multiple source, where only the first
|
48
|
+
dependency of a rule has any effect (Patch supplied by Emanuel
|
49
|
+
Inderm�hle)
|
50
|
+
|
51
|
+
* FileList#clone and FileList#dup have better sematics w.r.t. taint
|
52
|
+
and freeze.
|
53
|
+
|
54
|
+
* Changed from using Mutex to Monitor. Evidently Mutex causes thread
|
55
|
+
join errors when Ruby is compiled with -disable-pthreads. (Patch
|
56
|
+
supplied by Ittay Dror)
|
57
|
+
|
58
|
+
* Fixed bug in makefile parser that had problems with extra spaces in
|
59
|
+
file task names. (Patch supplied by Ittay Dror)
|
60
|
+
|
61
|
+
== Other changes in Version 0.8.2
|
62
|
+
|
63
|
+
* Added ENV var to rake's own Rakefile to prevent OS X from including
|
64
|
+
extended attribute junk in the rake package tar file. (Bug found by
|
65
|
+
Adam Majer)
|
66
|
+
|
67
|
+
* Added a performance patch for reading large makefile dependency
|
68
|
+
files. (Patch supplied by Ittay Dror)
|
69
|
+
|
70
|
+
== What is Rake
|
71
|
+
|
72
|
+
Rake is a build tool similar to the make program in many ways. But
|
73
|
+
instead of cryptic make recipes, Rake uses standard Ruby code to
|
74
|
+
declare tasks and dependencies. You have the full power of a modern
|
75
|
+
scripting language built right into your build tool.
|
76
|
+
|
77
|
+
== Availability
|
78
|
+
|
79
|
+
The easiest way to get and install rake is via RubyGems ...
|
80
|
+
|
81
|
+
gem install rake (you may need root/admin privileges)
|
82
|
+
|
83
|
+
Otherwise, you can get it from the more traditional places:
|
84
|
+
|
85
|
+
Home Page:: http://rake.rubyforge.org/
|
86
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
87
|
+
|
88
|
+
== Task Argument Examples
|
89
|
+
|
90
|
+
Prior to version 0.8.0, rake was only able to handle command line
|
91
|
+
arguments of the form NAME=VALUE that were passed into Rake via the
|
92
|
+
ENV hash. Many folks had asked for some kind of simple command line
|
93
|
+
arguments, perhaps using "--" to separate regular task names from
|
94
|
+
argument values on the command line. The problem is that there was no
|
95
|
+
easy way to associate positional arguments on the command line with
|
96
|
+
different tasks. Suppose both tasks :a and :b expect a command line
|
97
|
+
argument: does the first value go with :a? What if :b is run first?
|
98
|
+
Should it then get the first command line argument.
|
99
|
+
|
100
|
+
Rake 0.8.0 solves this problem by explicitly passing values directly
|
101
|
+
to the tasks that need them. For example, if I had a release task
|
102
|
+
that required a version number, I could say:
|
103
|
+
|
104
|
+
rake release[0.8.2]
|
105
|
+
|
106
|
+
And the string "0.8.2" will be passed to the :release task. Multiple
|
107
|
+
arguments can be passed by separating them with a comma, for example:
|
108
|
+
|
109
|
+
rake name[john,doe]
|
110
|
+
|
111
|
+
Just a few words of caution. The rake task name and its arguments
|
112
|
+
need to be a single command line argument to rake. This generally
|
113
|
+
means no spaces. If spaces are needed, then the entire rake +
|
114
|
+
argument string should be quoted. Something like this:
|
115
|
+
|
116
|
+
rake "name[billy bob, smith]"
|
117
|
+
|
118
|
+
(Quoting rules vary between operating systems and shells, so make sure
|
119
|
+
you consult the proper docs for your OS/shell).
|
120
|
+
|
121
|
+
=== Tasks that Expect Parameters
|
122
|
+
|
123
|
+
Parameters are only given to tasks that are setup to expect them. In
|
124
|
+
order to handle named parameters, the task declaration syntax for
|
125
|
+
tasks has been extended slightly.
|
126
|
+
|
127
|
+
For example, a task that needs a first name and last name might be
|
128
|
+
declared as:
|
129
|
+
|
130
|
+
task :name, :first_name, :last_name
|
131
|
+
|
132
|
+
The first argument is still the name of the task (:name in this case).
|
133
|
+
The next to argumements are the names of the parameters expected by
|
134
|
+
:name (:first_name and :last_name in the example).
|
135
|
+
|
136
|
+
To access the values of the paramters, the block defining the task
|
137
|
+
behaviour can now accept a second parameter:
|
138
|
+
|
139
|
+
task :name, :first_name, :last_name do |t, args|
|
140
|
+
puts "First name is #{args.first_name}"
|
141
|
+
puts "Last name is #{args.last_name}"
|
142
|
+
end
|
143
|
+
|
144
|
+
The first argument of the block "t" is always bound to the current
|
145
|
+
task object. The second argument "args" is an open-struct like object
|
146
|
+
that allows access to the task arguments. Extra command line
|
147
|
+
arguments to a task are ignored. Missing command line arguments are
|
148
|
+
given the nil value.
|
149
|
+
|
150
|
+
== Thanks
|
151
|
+
|
152
|
+
As usual, it was input from users that drove a alot of these changes. The
|
153
|
+
following people either contributed patches, made suggestions or made
|
154
|
+
otherwise helpful comments. Thanks to ...
|
155
|
+
|
156
|
+
* Edwin Pratomo
|
157
|
+
* Gavin Stark
|
158
|
+
* Adam Q. Salter
|
159
|
+
* Adam Majer
|
160
|
+
* Emanuel Inderm�hle
|
161
|
+
* Ittay Dror
|
162
|
+
* Bheeshmar Redheendran (for spending an afternoon with me debugging
|
163
|
+
windows issues)
|
164
|
+
|
165
|
+
-- Jim Weirich
|
@@ -0,0 +1,112 @@
|
|
1
|
+
= Rake 0.8.3 Released
|
2
|
+
|
3
|
+
Rake version 0.8.3 is a bug-fix release of rake.
|
4
|
+
|
5
|
+
== Changes
|
6
|
+
|
7
|
+
=== Bug Fixes in Version 0.8.3
|
8
|
+
|
9
|
+
* Enhanced the system directory detection in windows. We now check
|
10
|
+
HOMEDRIVE/HOMEPATH and USERPROFILE if APPDATA isn't found. (Patch
|
11
|
+
supplied by James Tucker). Rake no long aborts if it can't find the
|
12
|
+
directory.
|
13
|
+
|
14
|
+
* Added fix to handle ruby installations in directories with spaces in
|
15
|
+
their name.
|
16
|
+
|
17
|
+
== What is Rake
|
18
|
+
|
19
|
+
Rake is a build tool similar to the make program in many ways. But
|
20
|
+
instead of cryptic make recipes, Rake uses standard Ruby code to
|
21
|
+
declare tasks and dependencies. You have the full power of a modern
|
22
|
+
scripting language built right into your build tool.
|
23
|
+
|
24
|
+
== Availability
|
25
|
+
|
26
|
+
The easiest way to get and install rake is via RubyGems ...
|
27
|
+
|
28
|
+
gem install rake (you may need root/admin privileges)
|
29
|
+
|
30
|
+
Otherwise, you can get it from the more traditional places:
|
31
|
+
|
32
|
+
Home Page:: http://rake.rubyforge.org/
|
33
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
34
|
+
|
35
|
+
== Task Argument Examples
|
36
|
+
|
37
|
+
Prior to version 0.8.0, rake was only able to handle command line
|
38
|
+
arguments of the form NAME=VALUE that were passed into Rake via the
|
39
|
+
ENV hash. Many folks had asked for some kind of simple command line
|
40
|
+
arguments, perhaps using "--" to separate regular task names from
|
41
|
+
argument values on the command line. The problem is that there was no
|
42
|
+
easy way to associate positional arguments on the command line with
|
43
|
+
different tasks. Suppose both tasks :a and :b expect a command line
|
44
|
+
argument: does the first value go with :a? What if :b is run first?
|
45
|
+
Should it then get the first command line argument.
|
46
|
+
|
47
|
+
Rake 0.8.0 solves this problem by explicitly passing values directly
|
48
|
+
to the tasks that need them. For example, if I had a release task
|
49
|
+
that required a version number, I could say:
|
50
|
+
|
51
|
+
rake release[0.8.3]
|
52
|
+
|
53
|
+
And the string "0.8.3" will be passed to the :release task. Multiple
|
54
|
+
arguments can be passed by separating them with a comma, for example:
|
55
|
+
|
56
|
+
rake name[john,doe]
|
57
|
+
|
58
|
+
Just a few words of caution. The rake task name and its arguments
|
59
|
+
need to be a single command line argument to rake. This generally
|
60
|
+
means no spaces. If spaces are needed, then the entire rake +
|
61
|
+
argument string should be quoted. Something like this:
|
62
|
+
|
63
|
+
rake "name[billy bob, smith]"
|
64
|
+
|
65
|
+
(Quoting rules vary between operating systems and shells, so make sure
|
66
|
+
you consult the proper docs for your OS/shell).
|
67
|
+
|
68
|
+
=== Tasks that Expect Parameters
|
69
|
+
|
70
|
+
Parameters are only given to tasks that are setup to expect them. In
|
71
|
+
order to handle named parameters, the task declaration syntax for
|
72
|
+
tasks has been extended slightly.
|
73
|
+
|
74
|
+
For example, a task that needs a first name and last name might be
|
75
|
+
declared as:
|
76
|
+
|
77
|
+
task :name, :first_name, :last_name
|
78
|
+
|
79
|
+
The first argument is still the name of the task (:name in this case).
|
80
|
+
The next to argumements are the names of the parameters expected by
|
81
|
+
:name (:first_name and :last_name in the example).
|
82
|
+
|
83
|
+
To access the values of the paramters, the block defining the task
|
84
|
+
behaviour can now accept a second parameter:
|
85
|
+
|
86
|
+
task :name, :first_name, :last_name do |t, args|
|
87
|
+
puts "First name is #{args.first_name}"
|
88
|
+
puts "Last name is #{args.last_name}"
|
89
|
+
end
|
90
|
+
|
91
|
+
The first argument of the block "t" is always bound to the current
|
92
|
+
task object. The second argument "args" is an open-struct like object
|
93
|
+
that allows access to the task arguments. Extra command line
|
94
|
+
arguments to a task are ignored. Missing command line arguments are
|
95
|
+
given the nil value.
|
96
|
+
|
97
|
+
== Thanks
|
98
|
+
|
99
|
+
As usual, it was input from users that drove a alot of these changes. The
|
100
|
+
following people either contributed patches, made suggestions or made
|
101
|
+
otherwise helpful comments. Thanks to ...
|
102
|
+
|
103
|
+
* Edwin Pratomo
|
104
|
+
* Gavin Stark
|
105
|
+
* Adam Q. Salter
|
106
|
+
* Adam Majer
|
107
|
+
* Emanuel Inderm�hle
|
108
|
+
* Ittay Dror
|
109
|
+
* Bheeshmar Redheendran (for spending an afternoon with me debugging
|
110
|
+
windows issues)
|
111
|
+
|
112
|
+
-- Jim Weirich
|
@@ -0,0 +1,147 @@
|
|
1
|
+
= Rake 0.8.4 Released
|
2
|
+
|
3
|
+
Rake version 0.8.4 is a bug-fix release of rake.
|
4
|
+
|
5
|
+
NOTE: The version of Rake that comes with Ruby 1.9 has diverged
|
6
|
+
slightly from the core Rake code base. Rake 0.8.4 will work
|
7
|
+
with Ruby 1.9, but is not a strict upgrade for the Rake that
|
8
|
+
comes with Ruby 1.9. A (near) future release of Rake will unify
|
9
|
+
those two codebases.
|
10
|
+
|
11
|
+
== Letter Writing Campaign
|
12
|
+
|
13
|
+
Thanks to Aaron Patterson (@tenderlove) and Eric Hodel (@drbrain) for
|
14
|
+
their encouraging support in organizing a letter writing campaign to
|
15
|
+
lobby for the "Warning Free" release of rake 0.8.4. A special callout
|
16
|
+
goes to Jonathan D. Lord, Sr (Dr. Wingnut) whose postcard was the
|
17
|
+
first to actually reach me. (see
|
18
|
+
http://tenderlovemaking.com/2009/02/26/we-need-a-new-version-of-rake/
|
19
|
+
for details)
|
20
|
+
|
21
|
+
== Changes
|
22
|
+
|
23
|
+
=== New Features / Enhancements in Version 0.8.4
|
24
|
+
|
25
|
+
* Case is preserved on rakefile names. (patch from James
|
26
|
+
M. Lawrence/quix)
|
27
|
+
|
28
|
+
* Improved Rakefile case insensitivity testing (patch from Luis
|
29
|
+
Lavena).
|
30
|
+
|
31
|
+
* Windows system dir search order is now: HOME, HOMEDRIVE + HOMEPATH,
|
32
|
+
APPDATA, USERPROFILE (patch from Luis Lavena)
|
33
|
+
|
34
|
+
* MingGW is now recognized as a windows platform. (patch from Luis
|
35
|
+
Lavena)
|
36
|
+
|
37
|
+
=== Bug Fixes in Version 0.8.4
|
38
|
+
|
39
|
+
* Removed reference to manage_gem to fix the warning produced by the
|
40
|
+
gem package task.
|
41
|
+
|
42
|
+
* Fixed stray ARGV option problem that was interfering with
|
43
|
+
Test::Unit::Runner. (patch from Pivotal Labs)
|
44
|
+
|
45
|
+
=== Infrastructure Improvements in Version 0.8.4
|
46
|
+
|
47
|
+
* Numerous fixes to the windows test suite (patch from Luis Lavena).
|
48
|
+
|
49
|
+
* Improved Rakefile case insensitivity testing (patch from Luis
|
50
|
+
Lavena).
|
51
|
+
|
52
|
+
* Better support for windows paths in the test task (patch from Simon
|
53
|
+
Chiang/bahuvrihi)
|
54
|
+
|
55
|
+
== What is Rake
|
56
|
+
|
57
|
+
Rake is a build tool similar to the make program in many ways. But
|
58
|
+
instead of cryptic make recipes, Rake uses standard Ruby code to
|
59
|
+
declare tasks and dependencies. You have the full power of a modern
|
60
|
+
scripting language built right into your build tool.
|
61
|
+
|
62
|
+
== Availability
|
63
|
+
|
64
|
+
The easiest way to get and install rake is via RubyGems ...
|
65
|
+
|
66
|
+
gem install rake (you may need root/admin privileges)
|
67
|
+
|
68
|
+
Otherwise, you can get it from the more traditional places:
|
69
|
+
|
70
|
+
Home Page:: http://rake.rubyforge.org/
|
71
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
72
|
+
GitHub:: git://github.com/jimweirich/rake.git
|
73
|
+
|
74
|
+
== Task Argument Examples
|
75
|
+
|
76
|
+
Prior to version 0.8.0, rake was only able to handle command line
|
77
|
+
arguments of the form NAME=VALUE that were passed into Rake via the
|
78
|
+
ENV hash. Many folks had asked for some kind of simple command line
|
79
|
+
arguments, perhaps using "--" to separate regular task names from
|
80
|
+
argument values on the command line. The problem is that there was no
|
81
|
+
easy way to associate positional arguments on the command line with
|
82
|
+
different tasks. Suppose both tasks :a and :b expect a command line
|
83
|
+
argument: does the first value go with :a? What if :b is run first?
|
84
|
+
Should it then get the first command line argument.
|
85
|
+
|
86
|
+
Rake 0.8.0 solves this problem by explicitly passing values directly
|
87
|
+
to the tasks that need them. For example, if I had a release task
|
88
|
+
that required a version number, I could say:
|
89
|
+
|
90
|
+
rake release[0.8.4]
|
91
|
+
|
92
|
+
And the string "0.8.4" will be passed to the :release task. Multiple
|
93
|
+
arguments can be passed by separating them with a comma, for example:
|
94
|
+
|
95
|
+
rake name[john,doe]
|
96
|
+
|
97
|
+
Just a few words of caution. The rake task name and its arguments
|
98
|
+
need to be a single command line argument to rake. This generally
|
99
|
+
means no spaces. If spaces are needed, then the entire rake +
|
100
|
+
argument string should be quoted. Something like this:
|
101
|
+
|
102
|
+
rake "name[billy bob, smith]"
|
103
|
+
|
104
|
+
(Quoting rules vary between operating systems and shells, so make sure
|
105
|
+
you consult the proper docs for your OS/shell).
|
106
|
+
|
107
|
+
=== Tasks that Expect Parameters
|
108
|
+
|
109
|
+
Parameters are only given to tasks that are setup to expect them. In
|
110
|
+
order to handle named parameters, the task declaration syntax for
|
111
|
+
tasks has been extended slightly.
|
112
|
+
|
113
|
+
For example, a task that needs a first name and last name might be
|
114
|
+
declared as:
|
115
|
+
|
116
|
+
task :name, :first_name, :last_name
|
117
|
+
|
118
|
+
The first argument is still the name of the task (:name in this case).
|
119
|
+
The next to argumements are the names of the parameters expected by
|
120
|
+
:name (:first_name and :last_name in the example).
|
121
|
+
|
122
|
+
To access the values of the paramters, the block defining the task
|
123
|
+
behaviour can now accept a second parameter:
|
124
|
+
|
125
|
+
task :name, :first_name, :last_name do |t, args|
|
126
|
+
puts "First name is #{args.first_name}"
|
127
|
+
puts "Last name is #{args.last_name}"
|
128
|
+
end
|
129
|
+
|
130
|
+
The first argument of the block "t" is always bound to the current
|
131
|
+
task object. The second argument "args" is an open-struct like object
|
132
|
+
that allows access to the task arguments. Extra command line
|
133
|
+
arguments to a task are ignored. Missing command line arguments are
|
134
|
+
given the nil value.
|
135
|
+
|
136
|
+
== Thanks
|
137
|
+
|
138
|
+
As usual, it was input from users that drove a alot of these changes. The
|
139
|
+
following people either contributed patches, made suggestions or made
|
140
|
+
otherwise helpful comments. Thanks to ...
|
141
|
+
|
142
|
+
* James M. Lawrence/quix
|
143
|
+
* Luis Lavena
|
144
|
+
* Pivotal Labs
|
145
|
+
* Simon Chiang/bahuvrihi
|
146
|
+
|
147
|
+
-- Jim Weirich
|
@@ -0,0 +1,53 @@
|
|
1
|
+
= Rake 0.8.5 Released
|
2
|
+
|
3
|
+
Rake version 0.8.5 is a new release of Rake with greatly improved
|
4
|
+
support for executing commands on Windows. The "sh" command now has
|
5
|
+
the same semantics on Windows that it has on Unix based platforms.
|
6
|
+
|
7
|
+
== Changes
|
8
|
+
|
9
|
+
=== New Features / Enhancements in Version 0.8.5
|
10
|
+
|
11
|
+
* Improved implementation of the Rake system command for Windows.
|
12
|
+
(patch from James M. Lawrence/quix)
|
13
|
+
|
14
|
+
* Support for Ruby 1.9's improved system command. (patch from James
|
15
|
+
M. Lawrence/quix)
|
16
|
+
|
17
|
+
* Rake now includes the configured extension when invoking an
|
18
|
+
executable (Config::CONFIG['EXEEXT])
|
19
|
+
|
20
|
+
=== Bug Fixes in Version 0.8.5
|
21
|
+
|
22
|
+
* Environment variable keys are now correctly cased (it matters in
|
23
|
+
some implementations).
|
24
|
+
|
25
|
+
== What is Rake
|
26
|
+
|
27
|
+
Rake is a build tool similar to the make program in many ways. But
|
28
|
+
instead of cryptic make recipes, Rake uses standard Ruby code to
|
29
|
+
declare tasks and dependencies. You have the full power of a modern
|
30
|
+
scripting language built right into your build tool.
|
31
|
+
|
32
|
+
== Availability
|
33
|
+
|
34
|
+
The easiest way to get and install rake is via RubyGems ...
|
35
|
+
|
36
|
+
gem install rake (you may need root/admin privileges)
|
37
|
+
|
38
|
+
Otherwise, you can get it from the more traditional places:
|
39
|
+
|
40
|
+
Home Page:: http://rake.rubyforge.org/
|
41
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
42
|
+
GitHub:: git://github.com/jimweirich/rake.git
|
43
|
+
|
44
|
+
== Thanks
|
45
|
+
|
46
|
+
As usual, it was input from users that drove a alot of these changes. The
|
47
|
+
following people either contributed patches, made suggestions or made
|
48
|
+
otherwise helpful comments. Thanks to ...
|
49
|
+
|
50
|
+
* James M. Lawrence/quix
|
51
|
+
* Luis Lavena
|
52
|
+
|
53
|
+
-- Jim Weirich
|
@@ -0,0 +1,55 @@
|
|
1
|
+
= Rake 0.8.6 Released
|
2
|
+
|
3
|
+
Rake version 0.8.5 introduced greatly improved support for executing
|
4
|
+
commands on Windows. The "sh" command now has the same semantics on
|
5
|
+
Windows that it has on Unix based platforms.
|
6
|
+
|
7
|
+
Rake version 0.8.6 includes minor fixes the the RDoc generation.
|
8
|
+
|
9
|
+
== Changes
|
10
|
+
|
11
|
+
=== New Features / Enhancements in Version 0.8.5
|
12
|
+
|
13
|
+
* Improved implementation of the Rake system command for Windows.
|
14
|
+
(patch from James M. Lawrence/quix)
|
15
|
+
|
16
|
+
* Support for Ruby 1.9's improved system command. (patch from James
|
17
|
+
M. Lawrence/quix)
|
18
|
+
|
19
|
+
* Rake now includes the configured extension when invoking an
|
20
|
+
executable (Config::CONFIG['EXEEXT])
|
21
|
+
|
22
|
+
=== Bug Fixes in Version 0.8.5
|
23
|
+
|
24
|
+
* Environment variable keys are now correctly cased (it matters in
|
25
|
+
some implementations).
|
26
|
+
|
27
|
+
== What is Rake
|
28
|
+
|
29
|
+
Rake is a build tool similar to the make program in many ways. But
|
30
|
+
instead of cryptic make recipes, Rake uses standard Ruby code to
|
31
|
+
declare tasks and dependencies. You have the full power of a modern
|
32
|
+
scripting language built right into your build tool.
|
33
|
+
|
34
|
+
== Availability
|
35
|
+
|
36
|
+
The easiest way to get and install rake is via RubyGems ...
|
37
|
+
|
38
|
+
gem install rake (you may need root/admin privileges)
|
39
|
+
|
40
|
+
Otherwise, you can get it from the more traditional places:
|
41
|
+
|
42
|
+
Home Page:: http://rake.rubyforge.org/
|
43
|
+
Download:: http://rubyforge.org/project/showfiles.php?group_id=50
|
44
|
+
GitHub:: git://github.com/jimweirich/rake.git
|
45
|
+
|
46
|
+
== Thanks
|
47
|
+
|
48
|
+
As usual, it was input from users that drove a alot of these changes. The
|
49
|
+
following people either contributed patches, made suggestions or made
|
50
|
+
otherwise helpful comments. Thanks to ...
|
51
|
+
|
52
|
+
* James M. Lawrence/quix
|
53
|
+
* Luis Lavena
|
54
|
+
|
55
|
+
-- Jim Weirich
|