[pkgsrc/trunk]: pkgsrc/devel/ruby-kgio Update ruby-kgio to 2.11.0.

[taca <taca%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/fc6f4ba109be
branches:  trunk
changeset: 359532:fc6f4ba109be
user:      taca <taca%pkgsrc.org@localhost>
date:      Sun Mar 12 14:38:17 2017 +0000

description:
Update ruby-kgio to 2.11.0.

=== kgio 2.11.0 - reverting 2.10.0 breakage / 2016-12-16 22:56 UTC

  Mainly this release reverts back to kgio 2.9.3 behavior by
  supporting "autopush" functionality in the C extension.
  Removing this feature in 2.10.0 was a monumental mistake(*) on
  my part which caused a performance regression for ONE known user
  of kgio on the deprecated (but supported) Rainbows! server.

  This release does not affect known users outside of Rainbows!,
  but we may have unknown users, too.

  The attempt at a pure Ruby version of autopush had flaws and
  regressions in real-world testing, so that was abandoned.

  So yeah, kgio will be supported indefinitely even in the face
  of internal changes to MRI, but I strongly discourage its use
  for new projects.
  Users who only support Ruby 2.3 (and later) are encouraged to
  use `exception: false` with all *_nonblock methods.

  4 changes since 2.10.0:

        resurrect Kgio.autopush support in pure Ruby [REVERTED]
        reinstate the original (and dangerous) autopush in C
        TODO: update with Ruby 2.3 status
        test: increase test data sizes to fill socket buffers

  (*) - as was making this a separate project, at all

diffstat:

 devel/ruby-kgio/Makefile |   4 ++--
 devel/ruby-kgio/PLIST    |   3 ++-
 devel/ruby-kgio/distinfo |  10 +++++-----
 3 files changed, 9 insertions(+), 8 deletions(-)

diffs (44 lines):

diff -r 1a362744e96b -r fc6f4ba109be devel/ruby-kgio/Makefile
--- a/devel/ruby-kgio/Makefile  Sun Mar 12 14:34:32 2017 +0000
+++ b/devel/ruby-kgio/Makefile  Sun Mar 12 14:38:17 2017 +0000
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.9 2015/10/04 12:17:04 taca Exp $
+# $NetBSD: Makefile,v 1.10 2017/03/12 14:38:17 taca Exp $
 
-DISTNAME=      kgio-2.10.0
+DISTNAME=      kgio-2.11.0
 PKGNAME=       ${RUBY_PKGPREFIX}-${DISTNAME}
 CATEGORIES=    devel net
 
diff -r 1a362744e96b -r fc6f4ba109be devel/ruby-kgio/PLIST
--- a/devel/ruby-kgio/PLIST     Sun Mar 12 14:34:32 2017 +0000
+++ b/devel/ruby-kgio/PLIST     Sun Mar 12 14:38:17 2017 +0000
@@ -1,4 +1,4 @@
-@comment $NetBSD: PLIST,v 1.6 2015/10/04 12:17:04 taca Exp $
+@comment $NetBSD: PLIST,v 1.7 2017/03/12 14:38:17 taca Exp $
 ${GEM_HOME}/cache/${GEM_NAME}.gem
 ${GEM_EXTSDIR}/gem.build_complete
 ${GEM_EXTSDIR}/kgio_ext.${RUBY_DLEXT}
@@ -21,6 +21,7 @@
 ${GEM_LIBDIR}/archive/slrnpull.conf
 ${GEM_LIBDIR}/ext/kgio/accept.c
 ${GEM_LIBDIR}/ext/kgio/ancient_ruby.h
+${GEM_LIBDIR}/ext/kgio/autopush.c
 ${GEM_LIBDIR}/ext/kgio/blocking_io_region.h
 ${GEM_LIBDIR}/ext/kgio/broken_system_compat.h
 ${GEM_LIBDIR}/ext/kgio/connect.c
diff -r 1a362744e96b -r fc6f4ba109be devel/ruby-kgio/distinfo
--- a/devel/ruby-kgio/distinfo  Sun Mar 12 14:34:32 2017 +0000
+++ b/devel/ruby-kgio/distinfo  Sun Mar 12 14:38:17 2017 +0000
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.9 2015/11/03 03:29:24 agc Exp $
+$NetBSD: distinfo,v 1.10 2017/03/12 14:38:17 taca Exp $
 
-SHA1 (kgio-2.10.0.gem) = 10711f7697d97306af73a952ad489e859866cd44
-RMD160 (kgio-2.10.0.gem) = 3e579bf542194245cd4f444edf5652c060773a64
-SHA512 (kgio-2.10.0.gem) = 60cd698a9a6468abd83d94cf62f321a6014e6e5f964c6f67ae8ee98d401d9e37639f2bfbf9f307d56d0f5fc46d49cea6a3f8c8ed12073b065f8949335baa83af
-Size (kgio-2.10.0.gem) = 56320 bytes
+SHA1 (kgio-2.11.0.gem) = 4b31817f69a2efed9ba9c800c98c747a54a0f434
+RMD160 (kgio-2.11.0.gem) = c0b106a313d90b1950d564405280f9ec6a7fad5d
+SHA512 (kgio-2.11.0.gem) = aa5146e596ca8ca434b23edb780a64a39955f3d5c68c00746a5f0aae48b801dd06e5aa14b7456978ed80048a7c5ee2cd497c942054e08ffc46b724d4d8bce473
+Size (kgio-2.11.0.gem) = 59392 bytes