Import Debian changes 4.03-ok1
libjson-xs-perl (4.03-ok1) yangtze; urgency=medium * Build for openkylin.
This commit is contained in:
zhangyichun
parent
eae8ec5dcf
commit
16f1252873
|
|
@ -0,0 +1,8 @@
|
|||
libjson-xs-perl for Debian
|
||||
|
||||
Please edit this to provide information specific to
|
||||
this libjson-xs Debian package.
|
||||
|
||||
(Automatically generated by debmake Version 4.3.1)
|
||||
|
||||
-- zhangyichun <zhangyichun@kylinos.cn> Tue, 23 Aug 2022 15:39:25 +0800
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
libjson-xs-perl (4.03-ok1) yangtze; urgency=medium
|
||||
|
||||
* Build for openkylin.
|
||||
|
||||
-- zhangyichun <zhangyichun@kylinos.cn> Tue, 23 Aug 2022 15:39:25 +0800
|
||||
|
|
@ -0,0 +1,34 @@
|
|||
Source: libjson-xs-perl
|
||||
Section: perl
|
||||
Priority: optional
|
||||
Maintainer: OpenKylin Developers <packaging@list.openkylin.top>
|
||||
Build-Depends: debhelper-compat (= 13),
|
||||
libcanary-stability-perl,
|
||||
libcommon-sense-perl <!nocheck>,
|
||||
libtypes-serialiser-perl <!nocheck>,
|
||||
perl-xs-dev,
|
||||
perl:native
|
||||
Standards-Version: 4.5.0
|
||||
Vcs-Browser: https://gitee.com/openkylin/libjson-xs-perl
|
||||
Vcs-Git: https://gitee.com/openkylin/libjson-xs-perl.git
|
||||
Homepage: https://metacpan.org/release/JSON-XS
|
||||
Rules-Requires-Root: no
|
||||
|
||||
|
||||
Package: libjson-xs-perl
|
||||
Architecture: any
|
||||
Depends: ${misc:Depends},
|
||||
${perl:Depends},
|
||||
${shlibs:Depends},
|
||||
libcommon-sense-perl,
|
||||
libtypes-serialiser-perl
|
||||
Breaks: libjson-perl (<< 2.90)
|
||||
Description: module for manipulating JSON-formatted data (C/XS-accelerated)
|
||||
JSON::XS is a module for manipulating data stored in the JavaScript Object
|
||||
Notation (JSON) serialization format (defined in RFC 4627), which serves as
|
||||
an alternative to XML.
|
||||
.
|
||||
This C/XS-accelerated JSON implementation confers significant performance
|
||||
gains if available. After installing this package, any code using the JSON
|
||||
module (see libjson-perl) will automagically benefit from this.
|
||||
|
||||
|
|
@ -0,0 +1,119 @@
|
|||
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
|
||||
Upstream-Name: libjson-xs
|
||||
Source: <url://example.com>
|
||||
#
|
||||
# Please double check copyright with the licensecheck(1) command.
|
||||
|
||||
Files: Changes
|
||||
MANIFEST
|
||||
META.json
|
||||
META.yml
|
||||
Makefile.PL
|
||||
XS.xs
|
||||
XS/Boolean.pm
|
||||
eg/bench
|
||||
t/00_load.t
|
||||
t/01_utf8.t
|
||||
t/02_error.t
|
||||
t/03_types.t
|
||||
t/04_dwiw_encode.t
|
||||
t/05_dwiw_decode.t
|
||||
t/06_pc_pretty.t
|
||||
t/07_pc_esc.t
|
||||
t/08_pc_base.t
|
||||
t/09_pc_extra_number.t
|
||||
t/10_pc_keysort.t
|
||||
t/11_pc_expo.t
|
||||
t/12_blessed.t
|
||||
t/13_limit.t
|
||||
t/14_latin1.t
|
||||
t/15_prefix.t
|
||||
t/16_tied.t
|
||||
t/17_relaxed.t
|
||||
t/18_json_checker.t
|
||||
t/19_incr.t
|
||||
t/20_faihu.t
|
||||
t/21_evans.t
|
||||
t/22_comment_at_eof.t
|
||||
t/52_object.t
|
||||
t/99_binary.t
|
||||
typemap
|
||||
Copyright: __NO_COPYRIGHT_NOR_LICENSE__
|
||||
License: __NO_COPYRIGHT_NOR_LICENSE__
|
||||
|
||||
Files: README
|
||||
Copyright: __NO_COPYRIGHT__ in: README
|
||||
License: __UNKNOWN__
|
||||
personally bitten by this "JSON is YAML" lie, I refused and said I
|
||||
will continue to educate people about these issues, so others do not
|
||||
run into the same problem again and again. After this, Brian called
|
||||
me a (quote)*complete and worthless idiot*(unquote).
|
||||
.
|
||||
In my opinion, instead of pressuring and insulting people who
|
||||
actually clarify issues with YAML and the wrong statements of some
|
||||
of its proponents, I would kindly suggest reading the JSON spec
|
||||
(which is not that difficult or long) and finally make YAML
|
||||
compatible to it, and educating users about the changes, instead of
|
||||
spreading lies about the real compatibility for many *years* and
|
||||
trying to silence people who point out that it isn't true.
|
||||
.
|
||||
Addendum/2009: the YAML 1.2 spec is still incompatible with JSON,
|
||||
even though the incompatibilities have been documented (and are
|
||||
known to Brian) for many years and the spec makes explicit claims
|
||||
that YAML is a superset of JSON. It would be so easy to fix, but
|
||||
apparently, bullying people and corrupting userdata is so much
|
||||
easier.
|
||||
.
|
||||
SPEED
|
||||
It seems that JSON::XS is surprisingly fast, as shown in the following
|
||||
tables. They have been generated with the help of the "eg/bench" program
|
||||
in the JSON::XS distribution, to make it easy to compare on your own
|
||||
system.
|
||||
.
|
||||
First comes a comparison between various modules using a very short
|
||||
single-line JSON string (also available at
|
||||
<http://dist.schmorp.de/misc/json/short.json>).
|
||||
.
|
||||
{"method": "handleMessage", "params": ["user1",
|
||||
"we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7,
|
||||
1, 0]}
|
||||
.
|
||||
It shows the number of encodes/decodes per second (JSON::XS uses the
|
||||
functional interface, while JSON::XS/2 uses the OO interface with
|
||||
pretty-printing and hashkey sorting enabled, JSON::XS/3 enables shrink.
|
||||
JSON::DWIW/DS uses the deserialise function, while JSON::DWIW::FJ uses
|
||||
|
||||
Files: XS.pm
|
||||
Copyright: __NO_COPYRIGHT__ in: XS.pm
|
||||
License: __UNKNOWN__
|
||||
bitten by this "JSON is YAML" lie, I refused and said I will continue to
|
||||
educate people about these issues, so others do not run into the same
|
||||
problem again and again. After this, Brian called me a (quote)I<complete
|
||||
and worthless idiot>(unquote).
|
||||
.
|
||||
In my opinion, instead of pressuring and insulting people who actually
|
||||
clarify issues with YAML and the wrong statements of some of its
|
||||
proponents, I would kindly suggest reading the JSON spec (which is not
|
||||
that difficult or long) and finally make YAML compatible to it, and
|
||||
educating users about the changes, instead of spreading lies about the
|
||||
real compatibility for many I<years> and trying to silence people who
|
||||
point out that it isn't true.
|
||||
.
|
||||
Addendum/2009: the YAML 1.2 spec is still incompatible with JSON, even
|
||||
though the incompatibilities have been documented (and are known to Brian)
|
||||
for many years and the spec makes explicit claims that YAML is a superset
|
||||
of JSON. It would be so easy to fix, but apparently, bullying people and
|
||||
corrupting userdata is so much easier.
|
||||
|
||||
Files: bin/json_xs
|
||||
Copyright: 2008 Marc Lehmann <json@schmorp.de>
|
||||
License: __NO_LICENSE__
|
||||
|
||||
#----------------------------------------------------------------------------
|
||||
# Files marked as NO_LICENSE_TEXT_FOUND may be covered by the following
|
||||
# license/copyright files.
|
||||
|
||||
#----------------------------------------------------------------------------
|
||||
# License file: COPYING
|
||||
This module is licensed under the same terms as perl itself.
|
||||
.
|
||||
|
|
@ -0,0 +1 @@
|
|||
# You must remove unused comment lines for the released package.
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
#!/usr/bin/make -f
|
||||
|
||||
%:
|
||||
dh $@
|
||||
|
|
@ -0,0 +1 @@
|
|||
3.0 (quilt)
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
version=4
|
||||
opts=uversionmangle=s/\.(\d)$/.${1}00/;s/\.(\d\d)$/.${1}0/;s/\.(\d\d\d)(\d)$/.${1}.${2}/ \
|
||||
https://metacpan.org/release/JSON-XS .+/JSON-XS-v?@ANY_VERSION@@ARCHIVE_EXT@$
|
||||
|
||||
Loading…
Reference in New Issue