#
# spec file for package perl-Process
#
# 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 Process
Name:           perl-Process
Version:        0.300.0
Release:        0
# 0.30 -> normalize -> 0.300.0
%define cpan_version 0.30
License:        Artistic-1.0 OR GPL-1.0-or-later
Summary:        Objects that represent generic computational processes
URL:            https://metacpan.org/release/%{cpan_name}
Source0:        https://cpan.metacpan.org/authors/id/A/AD/ADAMK/%{cpan_name}-%{cpan_version}.tar.gz
Source1:        cpanspec.yml
Source100:      README.md
BuildArch:      noarch
BuildRequires:  perl
BuildRequires:  perl-macros
BuildRequires:  perl(ExtUtils::MakeMaker) >= 6.36
BuildRequires:  perl(File::Remove) >= 1.51
BuildRequires:  perl(IO::String)
BuildRequires:  perl(IPC::Run3) >= 0.034
BuildRequires:  perl(Params::Util) >= 0.10
BuildRequires:  perl(Probe::Perl) >= 0.01
BuildRequires:  perl(YAML::Tiny) >= 1.36
Requires:       perl(IO::String)
Requires:       perl(IPC::Run3) >= 0.034
Requires:       perl(Params::Util) >= 0.10
Requires:       perl(Probe::Perl) >= 0.01
Requires:       perl(YAML::Tiny) >= 1.36
Provides:       perl(Process) = %{version}
Provides:       perl(Process::Delegatable) = %{version}
Provides:       perl(Process::Infinite) = %{version}
Provides:       perl(Process::Launcher) = %{version}
Provides:       perl(Process::Packageable) = %{version}
Provides:       perl(Process::Probe) = %{version}
Provides:       perl(Process::Role::Serializable) = %{version}
Provides:       perl(Process::Serializable) = %{version}
Provides:       perl(Process::Storable) = %{version}
%undefine       __perllib_provides
%{perl_requires}

%description
There are a great number of situations in which you may want to model a
computational process as an object.

An implementation of this sort of object generally looks like the following
when somebody uses it.

  my $object = MyProcessThingy->new( ... );

  my $rv = $object->run;

  if ( $rv ) {
      print "Thingy ran ok";
  } else {
      print "Failed to run thingy";
  }

The 'Process' family of modules are intended to be used as base and role
classes for these types of objects. They are used to help identify process
objects, and enforce a common API on these objects.

The primary intent is to provide a common base for objects that will be
able to be used with various distributed processing systems, without itself
actually implementing any form of distributed system.

The scope of uses for Process includes solutions to address the following
scenarios.

* A single CPU on a single host

* Multiple CPUs on a single host

* Multiple hosts on a single network

* Hosts distributed across the internet

* Any processing resource accessible via any mechanism

To put it another way, this family of classes is intended to addresses the
separation of concerns between the processing of something, and the results
of something.

The actual ways in which the processes are run, and the handling of the
results of the process are outside the scope of these classes.

The 'Process' class itself is the root of all of these classes. In fact, it
is so abstract that it contains no functionality at all, and serves
primarily to indicate that an object obeys the general rules of a 'Process'
class.

Most of the basic 'Process' modules are similar. They define how your
object should behave (an API for a particular concept) without dictating a
particular implementation.

However, by using them, you are confirming to some processing system that
your objects will obey particular rules, and thus can interact sanely with
any processing system that follows the API.

%prep
%autosetup  -n %{cpan_name}-%{cpan_version}

%build
PERL_USE_UNSAFE_INC=1 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
%license LICENSE

%changelog