106 lines
4.1 KiB
RPMSpec
106 lines
4.1 KiB
RPMSpec
#
|
|
# spec file for package perl-Storable
|
|
#
|
|
# Copyright (c) 2024 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 Storable
|
|
Name: perl-Storable
|
|
Version: 3.25
|
|
Release: 0
|
|
License: Artistic-1.0 OR GPL-1.0-or-later
|
|
Summary: Persistence for Perl data structures
|
|
URL: https://metacpan.org/release/%{cpan_name}
|
|
Source0: https://cpan.metacpan.org/authors/id/N/NW/NWCLARK/%{cpan_name}-%{version}.tar.gz
|
|
Source1: cpanspec.yml
|
|
Source100: README.md
|
|
BuildRequires: perl
|
|
BuildRequires: perl-macros
|
|
BuildRequires: perl(ExtUtils::MakeMaker) >= 6.31
|
|
%{perl_requires}
|
|
|
|
%description
|
|
The Storable package brings persistence to your Perl data structures
|
|
containing SCALAR, ARRAY, HASH or REF objects, i.e. anything that can be
|
|
conveniently stored to disk and retrieved at a later time.
|
|
|
|
It can be used in the regular procedural way by calling 'store' with a
|
|
reference to the object to be stored, along with the file name where the
|
|
image should be written.
|
|
|
|
The routine returns 'undef' for I/O problems or other internal error, a
|
|
true value otherwise. Serious errors are propagated as a 'die' exception.
|
|
|
|
To retrieve data stored to disk, use 'retrieve' with a file name. The
|
|
objects stored into that file are recreated into memory for you, and a
|
|
_reference_ to the root object is returned. In case an I/O error occurs
|
|
while reading, 'undef' is returned instead. Other serious errors are
|
|
propagated via 'die'.
|
|
|
|
Since storage is performed recursively, you might want to stuff references
|
|
to objects that share a lot of common data into a single array or hash
|
|
table, and then store that object. That way, when you retrieve back the
|
|
whole thing, the objects will continue to share what they originally
|
|
shared.
|
|
|
|
At the cost of a slight header overhead, you may store to an already opened
|
|
file descriptor using the 'store_fd' routine, and retrieve from a file via
|
|
'fd_retrieve'. Those names aren't imported by default, so you will have to
|
|
do that explicitly if you need those routines. The file descriptor you
|
|
supply must be already opened, for read if you're going to retrieve and for
|
|
write if you wish to store.
|
|
|
|
store_fd(\%table, *STDOUT) || die "can't store to stdout\n";
|
|
$hashref = fd_retrieve(*STDIN);
|
|
|
|
You can also store data in network order to allow easy sharing across
|
|
multiple platforms, or when storing on a socket known to be remotely
|
|
connected. The routines to call have an initial 'n' prefix for _network_,
|
|
as in 'nstore' and 'nstore_fd'. At retrieval time, your data will be
|
|
correctly restored so you don't have to know whether you're restoring from
|
|
native or network ordered data. Double values are stored stringified to
|
|
ensure portability as well, at the slight risk of loosing some precision in
|
|
the last decimals.
|
|
|
|
When using 'fd_retrieve', objects are retrieved in sequence, one object
|
|
(i.e. one recursive tree) per associated 'store_fd'.
|
|
|
|
If you're more from the object-oriented camp, you can inherit from Storable
|
|
and directly store your objects by invoking 'store' as a method. The fact
|
|
that the root of the to-be-stored tree is a blessed reference (i.e. an
|
|
object) is special-cased so that the retrieve does not provide a reference
|
|
to that object but rather the blessed object reference itself. (Otherwise,
|
|
you'd get a reference to that blessed object).
|
|
|
|
%prep
|
|
%autosetup -n %{cpan_name}-%{version}
|
|
|
|
%build
|
|
perl Makefile.PL INSTALLDIRS=vendor OPTIMIZE="%{optflags}"
|
|
%make_build
|
|
|
|
%check
|
|
make test
|
|
|
|
%install
|
|
%perl_make_install
|
|
%perl_process_packlist
|
|
%perl_gen_filelist
|
|
|
|
%files -f %{name}.files
|
|
%doc ChangeLog README stacksize
|
|
|
|
%changelog
|