jscop 0.1.2 → 0.1.3

data/vendor/cache/ruby/2.6.0/gems/rake-10.5.0/doc/rational.rdoc

@@ -1,151 +0,0 @@
-= Why rake?
-
-Ok, let me state from the beginning that I never intended to write this
-code.  I'm not convinced it is useful, and I'm not convinced anyone
-would even be interested in it.  All I can say is that Why's onion truck
-must by been passing through the Ohio valley.
-
-What am I talking about? ... A Ruby version of Make.
-
-See, I can sense you cringing already, and I agree.  The world certainly
-doesn't need yet another reworking of the "make" program.  I mean, we
-already have "ant".  Isn't that enough?
-
-It started yesterday.  I was helping a coworker fix a problem in one of
-the Makefiles we use in our project.  Not a particularly tough problem,
-but during the course of the conversation I began lamenting some of the
-shortcomings of make.  In particular, in one of my makefiles I wanted to
-determine the name of a file dynamically and had to resort to some
-simple scripting (in Ruby) to make it work.  "Wouldn't it be nice if you
-could just use Ruby inside a Makefile" I said.
-
-My coworker (a recent convert to Ruby) agreed, but wondered what it
-would look like.  So I sketched the following on the whiteboard...
-
-    "What if you could specify the make tasks in Ruby, like this ..."
-
-      task "build" do
-        java_compile(...args, etc ...)
-      end
-
-    "The task function would register "build" as a target to be made,
-    and the block would be the action executed whenever the build
-    system determined that it was time to do the build target."
-
-We agreed that would be cool, but writing make from scratch would be WAY
-too much work.  And that was the end of that!
-
-... Except I couldn't get the thought out of my head.  What exactly
-would be needed to make the about syntax work as a make file?  Hmmm, you
-would need to register the tasks, you need some way of specifying
-dependencies between tasks, and some way of kicking off the process.
-Hey!  What if we did ... and fifteen minutes later I had a working
-prototype of Ruby make, complete with dependencies and actions.
-
-I showed the code to my coworker and we had a good laugh.  It was just
-about a page worth of code that reproduced an amazing amount of the
-functionality of make.  We were both truly stunned with the power of
-Ruby.
-
-But it didn't do everything make did.  In particular, it didn't have
-timestamp based file dependencies (where a file is rebuilt if any of its
-prerequisite files have a later timestamp).  Obviously THAT would be a
-pain to add and so Ruby Make would remain an interesting experiment.
-
-... Except as I walked back to my desk, I started thinking about what
-file based dependencies would really need.  Rats!  I was hooked again,
-and by adding a new class and two new methods, file/timestamp
-dependencies were implemented.
-
-Ok, now I was really hooked.  Last night (during CSI!) I massaged the
-code and cleaned it up a bit.  The result is a bare-bones replacement
-for make in exactly 100 lines of code.
-
-For the curious, you can see it at ...
-* doc/proto_rake.rdoc
-
-Oh, about the name.  When I wrote the example Ruby Make task on my
-whiteboard, my coworker exclaimed "Oh! I have the perfect name: Rake ...
-Get it?  Ruby-Make. Rake!"  He said he envisioned the tasks as leaves
-and Rake would clean them up  ... or something like that.  Anyways, the
-name stuck.
-
-Some quick examples ...
-
-A simple task to delete backup files ...
-
-   task :clean do
-     Dir['*~'].each {|fn| rm fn rescue nil}
-   end
-
-Note that task names are symbols (they are slightly easier to type
-than quoted strings ... but you may use quoted string if you would
-rather). Rake makes the methods of the FileUtils module directly
-available, so we take advantage of the <tt>rm</tt> command.  Also note
-the use of "rescue nil" to trap and ignore errors in the <tt>rm</tt>
-command.
-
-To run it, just type "rake clean".  Rake will automatically find a
-Rakefile in the current directory (or above!) and will invoke the
-targets named on the command line.  If there are no targets explicitly
-named, rake will invoke the task "default".
-
-Here's another task with dependencies ...
-
-   task :clobber => [:clean] do
-     rm_r "tempdir"
-   end
-
-Task :clobber depends upon task :clean, so :clean will be run before
-:clobber is executed.
-
-Files are specified by using the "file" command.  It is similar to the
-task command, except that the task name represents a file, and the task
-will be run only if the file doesn't exist, or if its modification time
-is earlier than any of its prerequisites.
-
-Here is a file based dependency that will compile "hello.cc" to
-"hello.o".
-
-   file "hello.cc"
-   file "hello.o" => ["hello.cc"] do |t|
-     srcfile = t.name.sub(/\.o$/, ".cc")
-     sh %{g++ #{srcfile} -c -o #{t.name}}
-   end
-
-I normally specify file tasks with string (rather than symbols).  Some
-file names can't be represented by symbols.  Plus it makes the
-distinction between them more clear to the casual reader.
-
-Currently writing a task for each and every file in the project would be
-tedious at best.  I envision a set of libraries to make this job
-easier.  For instance, perhaps something like this ...
-
-   require 'rake/ctools'
-   Dir['*.c'].each do |fn|
-     c_source_file(fn)
-   end
-
-where "c_source_file" will create all the tasks need to compile all the
-C source files in a directory.  Any number of useful libraries could be
-created for rake.
-
-That's it.  There's no documentation (other than whats in this
-message).  Does this sound interesting to anyone?  If so, I'll continue
-to clean it up and write it up and publish it on RAA.  Otherwise, I'll
-leave it as an interesting exercise and a tribute to the power of Ruby.
-
-Why /might/ rake be interesting to Ruby programmers.  I don't know,
-perhaps ...
-
-* No weird make syntax (only weird Ruby syntax :-)
-* No need to edit or read XML (a la ant)
-* Platform independent build scripts.
-* Will run anywhere Ruby exists, so no need to have "make" installed.
-  If you stay away from the "sys" command and use things like
-  'ftools', you can have a perfectly platform independent
-  build script.  Also rake is only 100 lines of code, so it can
-  easily be packaged along with the rest of your code.
-
-So ... Sorry for the long rambling message.  Like I said, I never
-intended to write this code at all.

data/vendor/cache/ruby/2.6.0/gems/rake-10.5.0/doc/release_notes/rake-0.4.14.rdoc

@@ -1,23 +0,0 @@
-= Rake 0.4.14 Released
-
-== Changes
-
-Version 0.4.14 is a compatibility fix to allow Rake's test task to
-work under Ruby 1.8.2.  A change in the Test::Unit autorun feature
-prevented Rake from running any tests.  This release fixes the
-problem.
-
-Rake 0.4.14 is the recommended release for anyone using Ruby 1.8.2.
-
-== What is Rake
-
-Rake is a build tool similar to the make program in many ways.  But
-instead of cryptic make recipes, Rake uses standard Ruby code to
-declare tasks and dependencies.  You have the full power of a modern
-scripting language built right into your build tool.
-
-== Availability
-
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50
-

data/vendor/cache/ruby/2.6.0/gems/rake-10.5.0/doc/release_notes/rake-0.4.15.rdoc

@@ -1,35 +0,0 @@
-= Rake 0.4.15 Released
-
-== Changes
-
-Version 0.4.15 is a bug fix update for the Ruby 1.8.2 compatibility
-changes.  This release includes:
-
-* Fixed a bug that prevented the TESTOPTS flag from working with the
-  revised for 1.8.2 test task.
-
-* Updated the docs on --trace to indicate that it also enables a full
-  backtrace on errors.
-
-* Several fixes for new warnings generated.
-
-== Mini-Roadmap
-
-I will continue to issue Rake updates in the 0.4.xx series as new
-Ruby-1.8.2 issues become manifest.  Once the codebase stabilizes, I
-will release a 0.5.0 version incorporating all the changes.  If you
-are not using Ruby-1.8.2 and wish to avoid version churn, I recommend
-staying with a release prior to Rake-0.4.14.
-
-== What is Rake
-
-Rake is a build tool similar to the make program in many ways.  But
-instead of cryptic make recipes, Rake uses standard Ruby code to
-declare tasks and dependencies.  You have the full power of a modern
-scripting language built right into your build tool.
-
-== Availability
-
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50
-

data/vendor/cache/ruby/2.6.0/gems/rake-10.5.0/doc/release_notes/rake-0.5.0.rdoc

@@ -1,53 +0,0 @@
-= Rake 0.5.0 Released
-
-It has been a long time in coming, but we finally have a new version
-of Rake available.
-
-== Changes
-
-* Fixed bug where missing intermediate file dependencies could cause
-  an abort with --trace or --dry-run.  (Brian Candler)
-
-* Recursive rules are now supported (Tilman Sauerbeck).
-
-* Added tar.gz and tar.bz2 support to package task (Tilman Sauerbeck).
-
-* Added warning option for the Test Task (requested by Eric Hodel).
-
-* The jamis rdoc template is only used if it exists.
-
-* Added fix for Ruby 1.8.2 test/unit and rails problem.
-
-* Added contributed rake man file. (Jani Monoses)
-
-* Fixed documentation that was lacking the Rake module name (Tilman
-  Sauerbeck).
-
-== What is Rake
-
-Rake is a build tool similar to the make program in many ways.  But
-instead of cryptic make recipes, Rake uses standard Ruby code to
-declare tasks and dependencies.  You have the full power of a modern
-scripting language built right into your build tool.
-
-== Availability
-
-The easiest way to get and install rake is via RubyGems ...
-
-  gem install rake    (you may need root/admin privileges)
-
-Otherwise, you can get it from the more traditional places:
-
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50
-
-== Thanks
-
-Lots of people provided input to this release.  Thanks to Tilman
-Sauerbeck for numerous patches, documentation fixes and suggestions.
-And for also pushing me to get this release out.  Also, thanks to
-Brian Candler for the finding and fixing --trace/dry-run fix.  That
-was an obscure bug.  Also to Eric Hodel for some good suggestions.
-
--- Jim Weirich
-

data/vendor/cache/ruby/2.6.0/gems/rake-10.5.0/doc/release_notes/rake-0.5.3.rdoc

@@ -1,78 +0,0 @@
-= Rake 0.5.3 Released
-
-Although it has only been two weeks since the last release, we have
-enough updates to the Rake program to make it time for another
-release.
-
-== Changes
-
-Here are the changes for version 0.5.3 ...
-
-* FileLists have been extensively changed so that they mimic the
-  behavior of real arrays even more closely.  In particular,
-  operations on FileLists that return a new collection (e.g. collect,
-  reject) will now return a FileList rather than an array.  In
-  addition, several places where FileLists were not properly expanded
-  before use have been fixed.
-
-* A method (+ext+) to simplify the handling of file extensions was
-  added to String and to Array.
-
-* The 'testrb' script in test/unit tends to silently swallow syntax
-  errors in test suites.  Because of that, the default test loader is
-  now a rake-provided script.  You can still use 'testrb' by setting
-  the loader flag in the test task to :testrb.  (See the API documents
-  for TestTask for all the loader flag values).
-
-* FileUtil methods (e.g. cp, mv, install) are now declared to be
-  private.  This will cut down on the interference with user defined
-  methods of the same name.
-
-* Fixed the verbose flag in the TestTask so that the test code is
-  controlled by the flag.  Also shortened up some failure messages.
-  (Thanks to Tobias Luetke for the suggestion).
-
-* Rules will now properly detect a task that can generate a source
-  file.  Previously rules would only consider source files that were
-  already present.
-
-* Added an +import+ command that allows Rake to dynamically import
-  dependendencies into a running Rake session.  The +import+ command
-  can run tasks to update the dependency file before loading them.
-  Dependency files can be in rake or make format, allowing rake to
-  work with tools designed to generate dependencies for make.
-
-== What is Rake
-
-Rake is a build tool similar to the make program in many ways.  But
-instead of cryptic make recipes, Rake uses standard Ruby code to
-declare tasks and dependencies.  You have the full power of a modern
-scripting language built right into your build tool.
-
-== Availability
-
-The easiest way to get and install rake is via RubyGems ...
-
-  gem install rake    (you may need root/admin privileges)
-
-Otherwise, you can get it from the more traditional places:
-
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50
-
-== Thanks
-
-As usual, it was input from users that drove a alot of these changes.
-Thanks to ...
-
-* Brian Gernhardt for the rules fix (especially for the patience to
-  explain the problem to me until I got what he was talking about).
-* Stefan Lang for pointing out problems in the dark corners of the
-  FileList implementation.
-* Alexey Verkhovsky pointing out the silently swallows syntax errors
-  in tests.
-* Tobias Luetke for beautifying the test task output.
-* Sam Roberts for some of the ideas behind dependency loading.
-
--- Jim Weirich
-

data/vendor/cache/ruby/2.6.0/gems/rake-10.5.0/doc/release_notes/rake-0.5.4.rdoc

@@ -1,46 +0,0 @@
-= Rake 0.5.4 Released
-
-Time for some minor bug fixes and small enhancements
-
-== Changes
-
-Here are the changes for version 0.5.4 ...
-
-* Added double quotes to the test runner.  This allows the location of
-  the tests (and runner) to be in a directory path that contains
-  spaces (e.g. "C:/Program Files/ruby/bin").
-
-* Added .svn to default ignore list.  Now subversion project metadata
-  is automatically ignored by Rake's FileList.
-
-* Updated FileList#include to support nested arrays and filelists.
-  FileLists are flat lists of file names.  Using a FileList in an
-  include will flatten out the nested file names.
-
-== What is Rake
-
-Rake is a build tool similar to the make program in many ways.  But
-instead of cryptic make recipes, Rake uses standard Ruby code to
-declare tasks and dependencies.  You have the full power of a modern
-scripting language built right into your build tool.
-
-== Availability
-
-The easiest way to get and install rake is via RubyGems ...
-
-  gem install rake    (you may need root/admin privileges)
-
-Otherwise, you can get it from the more traditional places:
-
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50
-
-== Thanks
-
-As usual, it was input from users that drove a alot of these changes.
-Thanks to ...
-
-* Tilman Sauerbeck for the nested FileList suggestion.
-* Josh Knowles for pointing out the spaces in directory name problem.
-
--- Jim Weirich

data/vendor/cache/ruby/2.6.0/gems/rake-10.5.0/doc/release_notes/rake-0.6.0.rdoc

@@ -1,141 +0,0 @@
-= Rake 0.6.0 Released
-
-Its time for some long requested enhancements and lots of bug fixes
-... And a whole new web page.
-
-== New Web Page
-
-The primary documentation for rake has moved from the RubyForge based
-wiki to its own Hieraki based web site.  Constant spam on the wiki
-made it a difficult to keep clean.  The new site will be easier to
-update and organize.
-
-Check out the new documentation at: http://docs.rubyrake.org
-
-We will be adding new documentation to the site as time goes on.
-
-In addition to the new docs page, make sure you check out Martin
-Fowlers article on rake at http://martinfowler.com/articles/rake.html
-
-== Changes
-
-=== New Features
-
-* Multiple prerequisites on Rake rules now allowed.  However, keep the
-  following in mind:
-
-  1. All the prerequisites of a rule must be available before a rule
-     is triggered, where "enabled" means (a) an existing file, (b) a
-     defined rule, or (c) another rule which also must be
-     trigger-able.
-  2. Rules are checked in order of definition, so it is important to
-     order your rules properly.  If a file can be created by two
-     different rules, put the more specific rule first (otherwise the
-     more general rule will trigger first and the specific one will
-     never be triggered).
-  3. The <tt>source</tt> method now returns the name of the first
-     prerequisite listed in the rule.  <tt>sources</tt> returns the
-     names of all the rule prerequisites, ordered as they are defined
-     in the rule.  If the task has other prerequisites not defined in
-     the rule (but defined in an explicit task definition), then they
-     will _not_ be included in the sources list.
-
-* FileLists may now use the egrep command.  This popular enhancement
-  is now a core part of the FileList object.  If you want to get a
-  list of all your to-dos, fixmes and TBD comments, add the following
-  to your Rakefile.
-
-    desc "Look for TODO and FIXME tags in the code"
-    task :todo do
-      FileList['**/*.rb'].egrep /#.*(FIXME|TODO|TBD)/
-    end
-
-* The <tt>investigation</tt> method was added to task object to dump
-  out some important values.  This makes it a bit easier to debug Rake
-  tasks.
-
-  For example, if you are having problems with a particular task, just
-  print it out:
-
-    task :huh do
-      puts Rake::Task['huh'].investigation
-    end
-
-* The Rake::TestTask class now supports a "ruby_opts" option to pass
-  arbitrary ruby options to a test subprocess.
-
-=== Some Incompatibilities
-
-* When using the <tt>ruby</tt> command to start a Ruby subprocess, the
-  Ruby interpreter that is currently running rake is used by default.
-  This makes it easier to use rake in an environment with multiple
-  ruby installation.  (Previously, the first ruby command found in the
-  PATH was used).
-
-  If you wish to chose a different Ruby interpreter, you can
-  explicitly choose the interpreter via the <tt>sh</tt> command.
-
-* The major rake classes (Task, FileTask, FileCreationTask, RakeApp)
-  have been moved out of the toplevel scope and are now accessible as
-  Rake::Task, Rake::FileTask, Rake::FileCreationTask and
-  Rake::Application.  If your Rakefile
-  directly references any one of these tasks, you may:
-
-  1. Update your Rakefile to use the new classnames
-  2. Use the --classic-namespace option on the rake command to get the
-     old behavior,
-  3. Add <code>require 'rake/classic_namespace'</code> to the
-     Rakefile to get the old behavior.
-
-  <tt>rake</tt> will print a rather annoying warning whenever a
-  deprecated class name is referenced without enabling classic
-  namespace.
-
-=== Bug Fixes
-
-* Several unit tests and functional tests were fixed to run better
-  under windows.
-
-* Directory tasks are now a specialized version of a File task.  A
-  directory task will only be triggered if it doesn't exist.  It will
-  not be triggered if it is out of date w.r.t. any of its
-  prerequisites.
-
-* Fixed a bug in the Rake::GemPackageTask class so that the gem now
-  properly contains the platform name.
-
-* Fixed a bug where a prerequisite on a <tt>file</tt> task would cause
-  an exception if the prerequisite did not exist.
-
-== What is Rake
-
-Rake is a build tool similar to the make program in many ways.  But
-instead of cryptic make recipes, Rake uses standard Ruby code to
-declare tasks and dependencies.  You have the full power of a modern
-scripting language built right into your build tool.
-
-== Availability
-
-The easiest way to get and install rake is via RubyGems ...
-
-  gem install rake    (you may need root/admin privileges)
-
-Otherwise, you can get it from the more traditional places:
-
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50
-
-== Thanks
-
-As usual, it was input from users that drove a alot of these changes.
-The following people either contributed patches, made suggestions or
-made otherwise helpful comments.  Thanks to ...
-
-* Greg Fast (better ruby_opt test options)
-* Kelly Felkins (requested by better namespace support)
-* Martin Fowler (suggested Task.investigation)
-* Stuart Jansen (send initial patch for multiple prerequisites).
-* Masao Mutch (better support for non-ruby Gem platforms)
-* Philipp Neubeck (patch for file task exception fix)
-
--- Jim Weirich

data/vendor/cache/ruby/2.6.0/gems/rake-10.5.0/doc/release_notes/rake-0.7.0.rdoc

@@ -1,119 +0,0 @@
-= Rake 0.7.0 Released
-
-These changes for Rake have been brewing for a long time.  Here they
-are, I hope you enjoy them.
-
-== Changes
-
-=== New Features
-
-* Name space support for task names (see below).
-
-* Prerequisites can be executed in parallel (see below).
-
-* Added safe_ln support for openAFS (via Ludvig Omholt).
-
-* RDoc defaults to internal (in-process) invocation.  The old behavior
-  is still available by setting the +external+ flag to true.
-
-* Rakefiles are now loaded with the expanded path to prevent
-  accidental polution from the Ruby load path.
-
-* Task objects my now be used in prerequisite lists directly.
-
-* Task objects (in addition to task names) may now be included in the
-  prerequisite list of a task.
-
-* Internals cleanup and refactoring.
-
-=== Bug Fixes
-
-* Compatibility fixes for Ruby 1.8.4 FileUtils changes.
-
-=== Namespaces
-
-Tasks can now be nested inside their own namespaces.  Tasks within one
-namespace will not accidently interfer with tasks named in a different
-namespace.
-
-For example:
-
-  namespace "main" do
-    task :build do
-      # Build the main program
-    end
-  end
-
-  namespace "samples" do
-    task :build do
-      # Build the sample programs
-    end
-  end
-
-  task :build_all => ["main:build", "samples:build"]
-
-Even though both tasks are named :build, they are separate tasks in
-their own namespaces.  The :build_all task (defined in the toplevel
-namespace) references both build tasks in its prerequisites.
-
-You may invoke each of the individual build tasks with the following
-commands:
-
-  rake main:build
-  rake samples:build
-
-Or invoke both via the :build_all command:
-
-  rake build_all
-
-Namespaces may be nested arbitrarily.  Since the name of file tasks
-correspond to the name of a file in the external file system,
-FileTasks are not affected by the namespaces.
-
-See the Rakefile format documentation (in the Rake API documents) for
-more information.
-
-=== Parallel Tasks
-
-Sometimes you have several tasks that can be executed in parallel.  By
-specifying these tasks as prerequisites to a +multitask+ task.
-
-In the following example the tasks copy_src, copy_doc and copy_bin
-will all execute in parallel in their own thread.
-
-  multitask :copy_files => [:copy_src, :copy_doc, :copy_bin] do
-    puts "All Copies Complete"
-  end
-
-== What is Rake
-
-Rake is a build tool similar to the make program in many ways.  But
-instead of cryptic make recipes, Rake uses standard Ruby code to
-declare tasks and dependencies.  You have the full power of a modern
-scripting language built right into your build tool.
-
-== Availability
-
-The easiest way to get and install rake is via RubyGems ...
-
-  gem install rake    (you may need root/admin privileges)
-
-Otherwise, you can get it from the more traditional places:
-
-Home Page:: http://rake.rubyforge.org/
-Download::  http://rubyforge.org/project/showfiles.php?group_id=50
-
-== Thanks
-
-As usual, it was input from users that drove a alot of these changes.
-The following people either contributed patches, made suggestions or
-made otherwise helpful comments.  Thanks to ...
-
-* Doug Young (inspriation for the parallel task)
-
-* David Heinemeier Hansson (for --trace message enhancement and for
-  pushing for namespace support).
-
-* Ludvig Omholt (for the openAFS fix)
-
--- Jim Weirich