drake 0.8.3.1.0.14 → 0.8.4.1.0.15

data/CHANGES

@@ -1,6 +1,33 @@
 
 = Rake Changelog
 
+== Version 0.8.4
+
+* Preserve case when locating rakefiles (patch from James
+  M. Lawrence/quix)
+
+* Better support for windows paths in the test task (patch from Simon
+  Chiang/bahuvrihi)
+
+* Windows system dir search order is now: HOME, HOMEDRIVE + HOMEPATH,
+  APPDATA, USERPROFILE (patch from Luis Lavena)
+
+* MingGW is now recognized as a windows platform.  (patch from Luis
+  Lavena)
+
+* Numerous fixes to the windows test suite (patch from Luis Lavena).
+
+* Improved Rakefile case insensitivity testing (patch from Luis
+  Lavena).
+
+* Fixed stray ARGV option problem that was interfering with
+  Test::Unit::Runner.
+
+* Fixed default verbose mode (was accidently changed to false).  
+
+* Removed reference to manage_gem to fix the warning produced by the
+  gem package task.
+
 == Version 0.8.3
 
 * Enhanced the system directory detection in windows. We now check

data/CHANGES.drake

@@ -1,6 +1,10 @@
 
 = Drake Changelog
 
+== Version 0.8.4.1.0.15
+
+* Merge with mainline rake-0.8.4.1.
+
 == Version 0.8.3.1.0.14
 
 * Merge with mainline rake-0.8.3.1.

data/README

@@ -23,7 +23,7 @@ or equivalently,
 Drake is 100% compatible with Rake.  The code path for
 <tt>--threads=1</tt> is effectively identical to that of Rake's.
 Drake passes all of Rake's unit tests, with any number of threads from
-1 to 1000 (that's the most I tested).
+1 to 1000 (the most tested).
 
 === Dependencies
 
@@ -54,8 +54,8 @@ complete; can't do _z_ until _y_ is complete; can't do _y_ until _x_
 is complete; therefore do _x_."  In this fashion the sequence
 _x_,_y_,_z_ is enforced.
 
-The problem of insufficient dependencies plagues Makefiles as well.
-Package maintainers affectionately call it "not j-safe."
+The problem of insufficient dependencies plagues Makefiles as well,
+and is sometimes called "not j-safe".
 
 === MultiTask
 
@@ -85,35 +85,24 @@ If on the other hand your build takes twenty minutes to complete, you
 may be interested in investing some time getting the full dependency
 tree correct in order to take advantage of multiple CPUs or cores.
 
-Though there is no way for Drake to fathom what <em>you</em> mean by a
-correct dependency, there is a tool available which helps you get
-closer to saying what you mean.
+Though Drake cannot fathom what <em>you</em> mean by a correct
+dependency, there is a tool available which may help you get closer to
+saying what you mean:
 
   % drake --rand[=SEED]
 
 This will randomize the order of sibling prerequisites for each task.
 When given the optional SEED string, it will call
-<tt>srand(SEED.hash)</tt> to produce the same permutation each time
-(String#hash produces the integer which is the seed).  The randomize
-option also disables +multitask+, making it a regular unthreaded
-+task+.
-
-Though this option may produce an error due to an unspecified
-dependency, at least it will be an error which is exactly the same on
-each run (with SEED).  In addition, you'll have the major debugging
+<tt>srand(SEED.hash)</tt> to produce the same permutation each time.
+The randomize option also disables +multitask+, making it a regular
++task+.  (In multi-threaded mode, +multitask+ is already a regular
++task+.)
+
+Though this option may produce an error due to unspecified
+dependencies, with SEED at least it will be an error which is exactly
+the same on each run.  In addition you'll have the major debugging
 advantage of using a single thread.
 
-This option will also work in multi-threaded mode.  After all, once
-<tt>-jN</tt> is running smoothly there is <em>still</em> no guarantee
-that you have it right.  However with each successful execution of
-<tt>drake -jN --rand</tt>, the probability of correctness approaches 1
-(though asymptotically so).
-
-(The only way to <em>prove</em> correctness is to test <em>all</em>
-such permutations, which for any non-trivial project would be
-prohibitively large, especially those which meaningfully benefit from
-<tt>-j</tt>.)
-
 == Links
 
 * Download: http://rubyforge.org/frs/?group_id=6530
@@ -152,7 +141,7 @@ WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
 = RAKE -- Ruby Make -- <em>master branch</em>
 
-Supporting Rake version: 0.8.2
+Supporting Rake version: 0.8.4
 
 This package contains Rake, a simple ruby build program with
 capabilities similar to make.
@@ -167,103 +156,126 @@ Rake has the following features:
 
 * Rake supports rule patterns to synthesize implicit tasks.
 
-*  Flexible FileLists that act like arrays but know about manipulating
-   file names and paths.
+* Flexible FileLists that act like arrays but know about manipulating
+  file names and paths.
 
-* A library of prepackaged tasks to make building rakefiles easier.
+* A library of prepackaged tasks to make building rakefiles easier. For example,
+  tasks for building tarballs, gems and RDoc output are provided.
 
-== Download
+* Supports parallel execution of tasks.
 
-The latest version of rake can be found at
-
-* http://rubyforge.org/project/showfiles.php?group_id=50
 
-== Source Repository
+== Installation
 
-Rake is currently hosted at github. The github web page is
-http://github.com/jimweirich/rake. The public git clone URL is
+=== Gem Installation
 
-* git://github.com/jimweirich/rake.git
+Download and install  rake with the following.
 
-== Installation
+   gem install rake
 
 === Normal Installation
 
-You can install rake with the following command.
+You can download the source tarball of the latest version of Rake from
+
+* http://rubyforge.org/project/showfiles.php?group_id=50
+
+Extract the tarball and run
 
   % ruby install.rb
 
 from its distribution directory.
 
-=== GEM Installation
+== Usage
 
-Download and install  rake with the following.
+=== Simple Example
 
-   gem install --remote rake
+First, you must write a "Rakefile" file which contains the build rules. Here's
+a simple example:
 
-=== Running the Rake Test Suite
+  task :default => [:test]
+  
+  task :test do
+    ruby "test/unittest.rb"
+  end
 
-If you wish to run the unit and functional tests that come with Rake:
+This Rakefile has two tasks:
 
-* Install the 'session' gem in order to run the functional tests. adf
-  asdf asdf
-* CD into the top project directory of rake.
-* Type one of the following:
+* A task named "test", which - upon invocation - will run a unit test file in
+  Ruby.
+* A task named "default". This task does nothing by itself, but it has exactly
+  one dependency, namely the "test" task. Invoking the "default" task will
+  cause Rake to invoke the "test" task as well.
 
-     rake                  # If you have a version of rake installed
-     ruby -Ilib bin/rake   # If you do not have a version of rake installed.
+Running the "rake" command without any options will cause it to run the
+"default" task in the Rakefile:
 
-== Online Resources
+  % ls
+  Rakefile     test/
+  % rake
+  (in /home/some_user/Projects/rake)
+  ruby test/unittest.rb
+  ....unit test output here...
 
-== Rake References
+Type "rake --help" for all available options.
 
-* Rake Documentation Home: http://docs.rubyrake.org
-* Rake Project Page: http://rubyforge.org/projects/rake
-* Rake API Documents: http://rake.rubyforge.org
-* Rake Source Code Repo:  http://github.com/jimweirich/rake
-* Rake Git Repo Clone URL: git://github.com/jimweirich/rake.git
-
-== Presentations and Articles about Rake
 
-* Jim Weirich's 2003 RubyConf presentation: http://onestepback.org/articles/buildingwithrake/
-* Martin Fowler's article on Rake: http://martinfowler.com/articles/rake.html
-
-=== Road Map
+=== More Information
 
-* If you want to see how to invoke rake to build your projects, read on.
-* If you want to see the format of a Rakefile, see
+* For details on Rake's command-line invocation, read
+  doc/command_line_usage.rdoc[http://rake.rubyforge.org/files/doc/command_line_usage_rdoc.html]
+* For details on writing Rakefiles, see
   doc/rakefile.rdoc[http://rake.rubyforge.org/files/doc/rakefile_rdoc.html].
-* If you want to see the original announcement of rake, see
+* For the original announcement of Rake, see
   doc/rational.rdoc[http://rake.rubyforge.org/files/doc/rational_rdoc.html].
-* If you want to see a glossary of terms, see
+* For a glossary of terms, see
   doc/glossary.rdoc[http://rake.rubyforge.org/files/doc/glossary_rdoc.html].
 
-== Simple Example
 
-Once installed, you can run rake as follows ...
+== Development
+
+=== Source Repository
+
+Rake is currently hosted at github. The github web page is
+http://github.com/jimweirich/rake. The public git clone URL is
 
-  % rake [options ...]  [VAR=VALUE ...]  [tasks...]
+* git://github.com/jimweirich/rake.git
 
-Type "rake --help" for an up-to-date option summary.
+=== Running the Rake Test Suite
 
-Invoking <tt>rake</tt> without any options or targets causes rake to
-look for a rakefile and invoke the default task in that rakefile.
+If you wish to run the unit and functional tests that come with Rake:
 
-For example, given a simple rakefile like this ...
+* Install the 'session' gem in order to run the functional tests.
+* CD into the top project directory of rake.
+* Type one of the following:
 
-  task :default => [:test]
+     rake                  # If you have a version of rake installed
+     ruby -Ilib bin/rake   # If you do not have a version of rake installed.
 
-  task :test do
-    ruby "test/unittest.rb"
-  end
+=== Issues and Bug Reports
 
-The command 
+Bugs, features requests and other issues can be logged at
 
-  $ rake
+* http://onestepback.org/redmine/projects/show/rake
 
-will invoke the +default+ task.  As +default+ satisfies its
-prerequisites, the +test+ task will run the unit tests for the
-package.
+You will need an account to before you can post issues.  Register at
+http://onestepback.org/redmine/account/register.  Or you can send me
+an email (at jim dot weirich at gmail dot com)
+
+
+== Online Resources
+
+=== Rake References
+
+* Rake Documentation Home: http://docs.rubyrake.org
+* Rake Project Page: http://rubyforge.org/projects/rake
+* Rake API Documents: http://rake.rubyforge.org
+* Rake Source Code Repo:  http://github.com/jimweirich/rake
+* Rake Git Repo Clone URL: git://github.com/jimweirich/rake.git
+
+=== Presentations and Articles about Rake
+
+* Jim Weirich's 2003 RubyConf presentation: http://onestepback.org/articles/buildingwithrake/
+* Martin Fowler's article on Rake: http://martinfowler.com/articles/rake.html
 
 == Other Make Reinvisionings ...
 
@@ -305,127 +317,15 @@ new feature to be submitted in the form of new unit tests.
 
 For other information, feel free to ask on the ruby-talk mailing list
 (which is mirrored to comp.lang.ruby) or contact
-mailto:jim@weirichhouse.org.
-
-----
-
-= Usage
-
-Rake is invoked from the command line using:
-
-   % rake [<em>options</em> ...]  [<em>VAR</em>=<em>VALUE</em>]  [<em>targets</em> ...]
-
-Options are:
-
-[<tt><em>name</em>=<em>value</em></tt>]
-    Set the environment variable <em>name</em> to <em>value</em>
-    during the execution of the <b>rake</b> command.  You can access
-    the value by using ENV['<em>name</em>'].  
-
-[<tt>--classic-namespace</tt> (-n)]
-    Import the Task, FileTask, and FileCreateTask into the top-level
-    scope to be compatible with older versions of Rake.  Alternatively
-    you can include the line <code>require
-    'rake/classic_namespace'</code> in your Rakefile to get the
-    classic behavior.
-
-[<tt>--describe</tt> _pattern_ (-D)]
-    Describe the tasks (matching optional PATTERN), then exit.
-
-[<tt>--dry-run</tt> (-n)]
-    Do a dry run.  Print the tasks invoked and executed, but do not
-    actually execute any of the actions.
-
-[<tt>--execute</tt> _code_ (-e)]
-    Execute some Ruby code and exit.
-
-[<tt>--execute-print</tt> _code_ (-p)]
-    Execute some Ruby code, print the result, and exit.
-
-[<tt>--execute-continue</tt> _code_ (-p)]
-    Execute some Ruby code, then continue with normal task processing.
-
-[<tt>--help</tt>  (-H)]
-    Display some help text and exit.
-
-[<tt>--libdir</tt> _directory_  (-I)]
-    Add _directory_ to the list of directories searched for require.
-
-[<tt>--nosearch</tt>  (-N)]
-    Do not search for a Rakefile in parent directories.
-
-[<tt>--prereqs</tt>  (-P)]
-    Display a list of all tasks and their immediate prerequisites.
-
-[<tt>--quiet</tt> (-q)]
-    Do not echo commands from FileUtils.
-
-[<tt>--rakefile</tt> _filename_ (-f)]
-    Use _filename_ as the name of the rakefile. The default rakefile
-    names are +rakefile+ and +Rakefile+ (with +rakefile+ taking
-    precedence). If the rakefile is not found in the current
-    directory, +rake+ will search parent directories for a match. The
-    directory where the Rakefile is found will become the current
-    directory for the actions executed in the Rakefile.
-
-[<tt>--rakelibdir</tt> _rakelibdir_ (-R)]
-    Auto-import any .rake files in RAKELIBDIR. (default is 'rakelib')
-
-[<tt>--require</tt> _name_ (-r)]
-    Require _name_ before executing the Rakefile.
-
-[<tt>--rules</tt>]
-    Trace the rules resolution.
-
-[<tt>--silent (-s)]
-    Like --quiet, but also suppresses the 'in directory' announcement.
-
-[<tt>--system</tt> (-g)]
-    Use the system wide (global) rakefiles. The project Rakefile is
-    ignored. By default, the system wide rakefiles are used only if no
-    project Rakefile is found. On Unix-like system, the system wide
-    rake files are located in $HOME/.rake. On a windows system they
-    are stored in $APPDATA/Rake.
-
-[<tt>--no-system</tt> (-G)]
-    Use the project level Rakefile, ignoring the system-wide (global)
-    rakefiles.
-
-[<tt>--tasks</tt> (-T)]
-    Display a list of the major tasks and their comments.  Comments
-    are defined using the "desc" command.
-
-[<tt>--trace</tt> (-t)]
-    Turn on invoke/execute tracing. Also enable full backtrace on
-    errors.
-
-[<tt>--usage</tt> (-h)]
-    Display a usage message and exit.
-
-[<tt>--verbose</tt> (-v)]
-    Echo the Sys commands to standard output.
-
-[<tt>--version</tt> (-V)]
-    Display the program version and exit.
-
-In addition, any command line option of the form
-<em>VAR</em>=<em>VALUE</em> will be added to the environment hash
-<tt>ENV</tt> and may be tested in the Rakefile.
-
----
-
-= Rakefile Format
-
-See doc/rakefile.rdoc[http://rake.rubyforge.org/files/doc/rakefile_rdoc.html]
-for details on the Rakefile format.
+jim dot weirich at gmail.com.
 
 ---
 
 = Other stuff
 
-Author::   Jim Weirich <jim@weirichhouse.org>
+Author::   Jim Weirich <jim.weirich@gmail.com>
 Requires:: Ruby 1.8.0 or later
-License::  Copyright 2003, 2004 by Jim Weirich.
+License::  Copyright 2003-2008 by Jim Weirich.
            Released under an MIT-style license.  See the LICENSE file
            included in the distribution.
 

data/Rakefile

@@ -148,13 +148,11 @@ end
 
 rd = Rake::RDocTask.new("rdoc") { |rdoc|
   rdoc.rdoc_dir = 'html'
-#  rdoc.template = 'kilmer'
-#  rdoc.template = 'css2'
   rdoc.template = 'doc/jamis.rb'
   rdoc.title    = "Drake: Distributed Rake"
   rdoc.options << '--line-numbers' << '--inline-source' <<
     '--main' << 'README' <<
-    '--title' <<  'Drake: Distributed Rake' 
+    '--title' << 'Drake: Distributed Rake' 
   rdoc.rdoc_files.include('README', 'MIT-LICENSE', 'TODO', 'CHANGES')
   rdoc.rdoc_files.include('lib/**/*.rb', 'doc/**/*.rdoc')
   rdoc.rdoc_files.exclude(/\bcontrib\b/)
@@ -189,7 +187,7 @@ else
 
     s.name = 'drake'
     s.version = $package_version
-    s.summary = "Ruby based make-like utility."
+    s.summary = "A fork of Rake supporting parallel task execution."
     s.description = <<-EOF
       Rake is a Make-like program implemented in Ruby. Tasks
       and dependencies are specified in standard Ruby syntax.