rubygem-rake-11_3-11.3.0-bp154.1.20

- changed naming of the package, as this is a versioned gem

- changed naming of the package, as this is a versioned gem

- update to version 11.3.0; no changelog found

- Fixed last pieces of new macros

- adapt to new rubygem packaging style

- updated to version 10.3.2
  Bug fixes:
  * Rake no longer infinitely loops when showing exception causes that refer to
  each other.  Bug #272 by Chris Bandy.
  * Fixed documentation typos.  Bug #275 by Jake Worth.

- updated to version 10.3.1
  Bug fixes:
  * Really stop reporting an error when cleaning already-deleted files.  Pull
  request #269 by Randy Coulman
  * Fixed infinite loop when cleaning already-deleted files on windows.
  === 10.3 / 2014-04-15
  Enhancements:
  * Added --build-all option to rake which treats all file prerequisites as
  out-of-date.  Pull request #254 by Andrew Gilbert.
  * Added Rake::NameSpace#scope.  Issue #263 by Jon San Miguel.
  Bug fixes:
  * Suppress org.jruby package files in rake error messages for JRuby users.
  Issue #213 by Charles Nutter.
  * Fixed typo, removed extra "h".  Pull request #267 by Hsing-Hui Hsu.
  * Rake no longer reports an error when cleaning already-deleted files.  Pull
  request #266 by Randy Coulman.
  * Consume stderr while determining CPU count to avoid hang.  Issue #268 by
  Albert Sun.

- updated to version 10.2.2
  Bug fixes:
  * Restored Ruby 1.8.7 compatibility

- updated to version 10.1.1, no changelog

- fix usage of update-alternatives

- updated to version 10.1.0
  New Features:
  * Add support for variable length task argument lists. If more actual
    arguments are supplied than named arguments, then the extra
    arguments values will be in args.extras.
  * Application name is not displayed in the help banner. (Previously
    "rake" was hardcoded, now rake-based applications can display their
    own names).

- updated to version 10.0.4

- use update-alternatives (new gem2rpm)

- updated to version 10.0.3, same changelog as 10.0.1...

- updated to version 10.0.2

- updated to version 10.0.1
  = Rake 10.0.1 Released
  "Jim, when will Rake reach version 1.0?"
  Over the past several years I've been asked that question at
  conferences, panels and over twitter. Due to historical reasons (or
  maybe just plain laziness) Rake has (incorrectly) been treating the
  second digit of the version as the major release number. So in my head
  Rake was already at version 9.
  Well, it's time to fix things. This next version of Rake drops old,
  crufty, backwards compatibility hacks such as top level constants, DSL
  methods defined in Object and numerous other features that are just no
  longer desired. It's also time to drop the leading zero from the
  version number as well and call this new version of rake what it
  really is: Version 10.
  So, welcome to Rake 10.0!
  Rake 10 is actually feature identical to the latest version of Rake 9
  (that would be the version spelled 0.9.3), *except* that Rake 10 drops
  all the sundry deprecated features that have accumulated over the years.
  If your Rakefile is up to date and current with all the new features
  of Rake 10, you are ready to go. If your Rakefile still uses a few
  deprecated feeatures, feel free to use Rake 9 (0.9.3) with the same
  feature set. Just be aware that future features will be in Rake 10
  family line.

- updated to version 10.0.0
  * Show only the interesting portion of the backtrace by default (James M. Lawrence).
  * Added --reduce-compat optiont to remove backward compatible DSL hacks (James M. Lawrence).
  * lib/rake/file_list.rb (Rake::FileList#egrep): there is no need to
  open files in binary mode. (NAKAMURA Usaku)

- use new gem2rpm to provide new provisions

- make sure we do not compile against ruby19 - it won't work

- update to 0.9.2.2
  * The rake test loader now removes arguments it has processed.  Issue #51
  * Rake::TaskArguments now responds to #values_at
  * RakeFileUtils.verbose_flag = nil silences output the same as 0.8.7
  * Rake tests are now directory-independent
  * Rake tests are no longer require flexmock
  * Commands constant is no longer polluting top level namespace.