Update ruby-hitimes to 2.0.0.
pkgsrc change: add "USE_LANGAUGES= # none".
## Version 2.0.0 2019-09-23
* Remove the C and Java extensions as `Process.clock_gettime()` has the same
resolution as what the extensions did.
* Update all depedencies and resolve deprecations
* Now usable on truffleruby
## Version 1.3.1 2019-01-18
* Update jruby extension to not use global runtime state (thanks @kares) (#70)
* Update travis CI config
* Update documentataion for Ruby 2.6
# Hitimes Changelog
## Version 1.3.0 2018-06-15
* Add api method `Hitimes.raw_instant` to expose raw OS instant value
* Add api constant `Hitimes::INSTANT_CONVERSION_FACTOR` to expose raw OS instant conversion factor
* other development cleanup tasks
## Version 1.2.5 2017-05-25
* Update dependencies
* Add ruby 2.4 to windows fatbinary
* Update docs to indicate windows ruby before 2.0 is no longer supported
---------------------------------
## Version 1.2.4 2016-05-01
* Fix finding the extension on ruby 2.1.10 (thanks @wpiekutowski)
* Add more readable load error (thanks @mbautin)
* Update README with what versions of ruby are supported.
Problems found with mismatching existing digests for:
distfiles/asclock-classic-1.0.tar.gz
distfiles/asclock-gtk-2.1.10beta.tar.gz
distfiles/asclock-xlib-2.0.11.tar.gz
distfiles/emiclock-2.0.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
## Version 1.2.3 2015-09-13
* Release new fatbinary version for windows
* Update README to indicate duration units
* Provide a more friendly error message if the gem is not installed correctly
Hitimes is a fast, high resolution timer library for recording
performance metrics. It uses the appropriate low method calls for each
system to get the highest granularity time increments possible.
It currently supports any of the following systems:
* any system with the POSIX call `clock_gettime()`
* Mac OS X
* Windows
* JRuby
Using Hitimes can be faster than using a series of `Time.new` calls, and
it will have a much higher granularity. It is definitely faster than
using `Process.times`.
