ruby-nokogiri: update to 1.12.4.

Upstream changes
https://github.com/sparklemotion/nokogiri/releases/tag/v1.12.4

1.12.4 / 2021-08-29

Notable fix: Namespace inheritance

Namespace behavior when reparenting nodes has historically been poorly
specified and the behavior diverged between CRuby and JRuby. As a result,
making this behavior consistent in v1.12.0 introduced a breaking change.

This patch release reverts the Builder behavior present in v1.12.0..v1.12.3 but
keeps the Document behavior. This release also introduces a Document attribute
to allow affected users to easily change this behavior for their legacy code
without invasive changes.

Compensating Feature in XML::Document

This release of Nokogiri introduces a new Document boolean attribute,
namespace_inheritance, which controls whether children should inherit a
namespace when they are reparented. Nokogiri::XML:Document defaults this
attribute to false meaning "do not inherit," thereby making explicit the
behavior change introduced in v1.12.0.

CRuby users who desire the pre-v1.12.0 behavior may set
document.namespace_inheritance = true before reparenting nodes.

See https://nokogiri.org/rdoc/Nokogiri/XML/Document.html#
namespace_inheritance-instance_method for example usage.

Fix for XML::Builder

However, recognizing that we want Builder-created children to inherit
namespaces, Builder now will set namespace_inheritance=true on the underlying
document for both JRuby and CRuby. This means that, on CRuby, the pre-v1.12.0
behavior is restored.

Users who want to turn this behavior off may pass a keyword argument to the
Builder constructor like so:

Nokogiri::XML::Builder.new(namespace_inheritance: false)

See https://nokogiri.org/rdoc/Nokogiri/XML/Builder.html#
label-Namespace+inheritance for example usage.

Downstream gem maintainers

Note that any downstream gems may want to specifically omit Nokogiri
v1.12.0--v1.12.3 from their dependency specification if they rely on child
namespace inheritance:

Gem::Specification.new do |gem|
  # ...
  gem.add_runtime_dependency 'nokogiri', '!=1.12.3', '!=1.12.2', '!=1.12.1', '!=1.12.0'
  # ...
end

Fixed

  * [JRuby] Fix NPE in Schema parsing when an imported resource doesn't have a
    systemId. [#2296] (Thanks, @pepijnve!)

2 files changed, 7 insertions, 7 deletions

diff --git a/textproc/ruby-nokogiri/Makefile b/textproc/ruby-nokogiri/Makefile
index 3e9db696c67..f6c9220e9c1 100644
--- a/textproc/ruby-nokogiri/Makefile
+++ b/textproc/ruby-nokogiri/Makefile
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.60 2021/08/21 18:27:13 tsutsui Exp $
+# $NetBSD: Makefile,v 1.61 2021/09/11 09:54:46 tsutsui Exp $
 
-DISTNAME=	nokogiri-1.12.3
+DISTNAME=	nokogiri-1.12.4
 CATEGORIES=	textproc
 
 MAINTAINER=	tsutsui@NetBSD.org
diff --git a/textproc/ruby-nokogiri/distinfo b/textproc/ruby-nokogiri/distinfo
index ee389f6c46b..05b1329392c 100644
--- a/textproc/ruby-nokogiri/distinfo
+++ b/textproc/ruby-nokogiri/distinfo
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.41 2021/08/21 18:27:13 tsutsui Exp $
+$NetBSD: distinfo,v 1.42 2021/09/11 09:54:46 tsutsui Exp $
 
-SHA1 (nokogiri-1.12.3.gem) = 5a4330c996b00adae6629b3b067267561c0f23bb
-RMD160 (nokogiri-1.12.3.gem) = 0b631700c992fe82ea9dbcff565439e7742f8c26
-SHA512 (nokogiri-1.12.3.gem) = cb59e63641d49bc12a510e4c2af9af05b90520c9333680d8de7d18112a8bf569d8fc2df18286855946aa54c95058eb2cf42cb3e23b37fe7ca401544879fbbb41
-Size (nokogiri-1.12.3.gem) = 9588224 bytes
+SHA1 (nokogiri-1.12.4.gem) = 0eb79e072c21a25d0131e143b69a963944306438
+RMD160 (nokogiri-1.12.4.gem) = cc3550259ed66d0a2871622c102050eca6d497c2
+SHA512 (nokogiri-1.12.4.gem) = cc590261b4fb475cd34cebf7cfb94d3a673250487e6f3b25923cfc689bb055aab1e16b727388becf2a2f0236801053495e5caaf25cbcd9e849da56b365f20dcb
+Size (nokogiri-1.12.4.gem) = 9588736 bytes