There's an annoying bug that can occur when JSON.pm and JSON::XS are loaded into the same process with JSON::XS > 3.0 and JSON.pm < 2.90 https://metacpan.org/pod/JSON::Any#WARNING https://metacpan.org/diff/file?target=MAKAMAKA/JSON-2.90/&source=MAKAMAKA/JSON-2.61/#Changes Additionally, Installing JSON::XS > 3.0 breaks JSON::Any < 1.31, because the flow control iterates a list of potentials, sees that JSON::XS is installed, and attempts to use it, only to discover the API breakage JSON::XS 3.0 introduced. And this causes a vauge death condition of > perl -MJSON::Any -E1 > Couldn't find a decoder method. at -e line 0. > BEGIN failed--compilation aborted And to be clear, its not likely to be as straight forward as stipulating more minimum versions, because: - many of these components might cause circular deps. ( ie: JSON::XS can't depend on JSON::Any ) - some of these deps are || ( ) options ( leading to a minimum version being stipulated on a non-chosen path not having the right effect at runtime ) Summary: >=dev-perl/JSON-XS-3.0 breaks dev-perl/JSON < 2.90 breaks dev-perl/JSON-Any < 1.31 However: - JSON-XS should not require dev-perl/JSON - JSON-XS should not require JSON-Any
!<dev-perl/JSON-2.900.0 !<dev-perl/JSON-Any-1.310.0 Added blockers