libcpanel-json-xs-perl 3.0210-1ubuntu1 source package in Ubuntu

Changelog

libcpanel-json-xs-perl (3.0210-1ubuntu1) xenial; urgency=medium

  * Remove build-dependency on libmojolicious-perl; it's not worth pulling
    all this into main just for a test.  Add it to the dependencies of the
    "smoke" autopkgtest instead.

 -- Colin Watson <email address hidden>  Mon, 28 Dec 2015 03:37:42 +0000

Upload details

Uploaded by:
Colin Watson
Uploaded to:
Xenial
Original maintainer:
Ubuntu Developers
Architectures:
any
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Xenial release universe misc

Downloads

File Size SHA-256 Checksum
libcpanel-json-xs-perl_3.0210.orig.tar.gz 160.2 KiB 92d2790cb002fb1a3fe091ad6b90ad0464bffc4671e16ebb2378f3160f357360
libcpanel-json-xs-perl_3.0210-1ubuntu1.debian.tar.xz 2.8 KiB 64d16220773345f7def41a8179bfb5fa625603c04c0f7bfb28177311e04c92a9
libcpanel-json-xs-perl_3.0210-1ubuntu1.dsc 2.3 KiB 070b52fc20a3d5d188b63eb3e8a3ca61d40d9733baa986003dd08abb0dfc1eae

View changes file

Binary packages built by this source

libcpanel-json-xs-perl: module for fast and correct serialising to JSON

 Cpanel::JSON::XS converts Perl data structures to JSON and vice versa. Its
 primary goal is to be correct and its secondary goal is to be fast. To reach
 the latter goal it was written in C.
 .
 As this is the n-th-something JSON module on CPAN, what was the reason to
 write yet another JSON module? While it seems there are many JSON modules,
 none of them correctly handle all corner cases, and in most cases their
 maintainers are unresponsive, gone missing, or not listening to bug reports
 for other reasons.

libcpanel-json-xs-perl-dbgsym: debug symbols for package libcpanel-json-xs-perl

 Cpanel::JSON::XS converts Perl data structures to JSON and vice versa. Its
 primary goal is to be correct and its secondary goal is to be fast. To reach
 the latter goal it was written in C.
 .
 As this is the n-th-something JSON module on CPAN, what was the reason to
 write yet another JSON module? While it seems there are many JSON modules,
 none of them correctly handle all corner cases, and in most cases their
 maintainers are unresponsive, gone missing, or not listening to bug reports
 for other reasons.