File perl-Yote.spec of Package perl-Yote

Overview Repositories Revisions Requests Users Attributes Meta

File perl-Yote.spec of Package perl-Yote

#
# spec file for package perl-Yote
#
# Copyright (c) 2019 SUSE LINUX GmbH, Nuernberg, Germany.
#
# 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/
#

Name:           perl-Yote
Version:        3.0
Release:        0
%define cpan_name Yote
Summary:        Persistant Perl container objects in a directed graph of lazilly
License:        Artistic-1.0 OR GPL-1.0-or-later
Group:          Development/Libraries/Perl
Url:            https://metacpan.org/release/%{cpan_name}
Source0:        https://cpan.metacpan.org/authors/id/C/CA/CANID/%{cpan_name}-%{version}.tar.gz
BuildArch:      noarch
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildRequires:  perl
BuildRequires:  perl-macros
BuildRequires:  perl(Data::RecordStore) >= 3.15
BuildRequires:  perl(Module::Build) >= 0.420000
Requires:       perl(Data::RecordStore) >= 3.15
%{perl_requires}

%description
This is for anyone who wants to store arbitrary structured state data and
doesn't have the time or inclination to write a schema or configure some
framework. This can be used orthagonally to any other storage system.

Yote only loads data as it needs too. It does not load all stored
containers at once. Data is stored in a data directory and is stored using
the Data::RecordStore module. A Yote container is a key/value store where
the values can be strings, numbers, arrays, hashes or other Yote
containers.

The entry point for all Yote data stores is the root node. All objects in
the store are unreachable if they cannot trace a reference path back to
this node. If they cannot, running compress_store will remove them.

There are lots of potential uses for Yote, and a few come to mind :

* configuration data
 * data modeling
 * user preference data
 * user account data
 * game data
 * shopping carts
 * product information

%prep
%setup -q -n %{cpan_name}-%{version}
find . -type f ! -name \*.pl -print0 | xargs -0 chmod 644

%build
perl Build.PL installdirs=vendor
./Build build flags=%{?_smp_mflags}

%check
./Build test

%install
./Build install destdir=%{buildroot} create_packlist=0
%perl_gen_filelist

%files -f %{name}.files
%defattr(-,root,root,755)
%doc ChangeLog README VERSIONS
%license LICENSE

%changelog

Places

File perl-Yote.spec of Package perl-Yote

Places