125 lines
3.9 KiB
RPMSpec
125 lines
3.9 KiB
RPMSpec
![]() |
#
|
||
|
# spec file for package perl-Process (Version 0.28)
|
||
|
#
|
||
|
# Copyright (c) 2011 SUSE LINUX Products 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 http://bugs.opensuse.org/
|
||
|
#
|
||
|
|
||
|
Name: perl-Process
|
||
|
Version: 0.28
|
||
|
Release: 1
|
||
|
License: GPL+ or Artistic
|
||
|
%define cpan_name Process
|
||
|
Summary: Objects that represent generic computational processes
|
||
|
Url: http://search.cpan.org/dist/Process/
|
||
|
Group: Development/Libraries/Perl
|
||
|
Source: http://www.cpan.org/authors/id/A/AD/ADAMK/%{cpan_name}-%{version}.tar.gz
|
||
|
BuildArch: noarch
|
||
|
BuildRoot: %{_tmppath}/%{name}-%{version}-build
|
||
|
BuildRequires: perl
|
||
|
BuildRequires: perl-macros
|
||
|
BuildRequires: perl(File::Remove) >= 1.40
|
||
|
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
|
||
|
%{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
|
||
|
%setup -q -n %{cpan_name}-%{version}
|
||
|
|
||
|
%build
|
||
|
%{__perl} Makefile.PL INSTALLDIRS=vendor
|
||
|
%{__make} %{?_smp_mflags}
|
||
|
|
||
|
%check
|
||
|
%{__make} test
|
||
|
|
||
|
%install
|
||
|
%perl_make_install
|
||
|
%perl_process_packlist
|
||
|
%perl_gen_filelist
|
||
|
|
||
|
%clean
|
||
|
%{__rm} -rf %{buildroot}
|
||
|
|
||
|
%files -f %{name}.files
|
||
|
%defattr(-,root,root,755)
|
||
|
%doc Changes LICENSE README
|
||
|
|
||
|
%changelog
|