70 lines
2.3 KiB
RPMSpec
70 lines
2.3 KiB
RPMSpec
#
|
|
# spec file for package perl-JSON
|
|
#
|
|
# Copyright (c) 2022 SUSE LLC
|
|
#
|
|
# All modifications and additions to the file contributed by third parties
|
|
# remain the property of their copyright owners, unless otherwise agreed
|
|
# upon. The license for this file, and modifications and additions to the
|
|
# file, is the same license as for the pristine package itself (unless the
|
|
# license for the pristine package is not an Open Source License, in which
|
|
# case the license is the MIT License). An "Open Source License" is a
|
|
# license that conforms to the Open Source Definition (Version 1.9)
|
|
# published by the Open Source Initiative.
|
|
|
|
# Please submit bugfixes or comments via https://bugs.opensuse.org/
|
|
#
|
|
|
|
|
|
%define cpan_name JSON
|
|
Name: perl-JSON
|
|
Version: 4.10
|
|
Release: 0
|
|
License: Artistic-1.0 OR GPL-1.0-or-later
|
|
Summary: JSON (JavaScript Object Notation) encoder/decoder
|
|
URL: https://metacpan.org/release/%{cpan_name}
|
|
Source0: https://cpan.metacpan.org/authors/id/I/IS/ISHIGAKI/%{cpan_name}-%{version}.tar.gz
|
|
Source1: cpanspec.yml
|
|
BuildArch: noarch
|
|
BuildRequires: perl
|
|
BuildRequires: perl-macros
|
|
Recommends: perl(JSON::XS) >= 2.34
|
|
%{perl_requires}
|
|
|
|
%description
|
|
This module is a thin wrapper for JSON::XS-compatible modules with a few
|
|
additional features. All the backend modules convert a Perl data structure
|
|
to a JSON text and vice versa. This module uses JSON::XS by default, and
|
|
when JSON::XS is not available, falls back on JSON::PP, which is in the
|
|
Perl core since 5.14. If JSON::PP is not available either, this module then
|
|
falls back on JSON::backportPP (which is actually JSON::PP in a different
|
|
.pm file) bundled in the same distribution as this module. You can also
|
|
explicitly specify to use Cpanel::JSON::XS, a fork of JSON::XS by Reini
|
|
Urban.
|
|
|
|
All these backend modules have slight incompatibilities between them,
|
|
including extra features that other modules don't support, but as long as
|
|
you use only common features (most important ones are described below),
|
|
migration from backend to backend should be reasonably easy. For details,
|
|
see each backend module you use.
|
|
|
|
%prep
|
|
%autosetup -n %{cpan_name}-%{version}
|
|
|
|
%build
|
|
perl Makefile.PL INSTALLDIRS=vendor
|
|
%make_build
|
|
|
|
%check
|
|
make test
|
|
|
|
%install
|
|
%perl_make_install
|
|
%perl_process_packlist
|
|
%perl_gen_filelist
|
|
|
|
%files -f %{name}.files
|
|
%doc Changes README
|
|
|
|
%changelog
|