File perl-Algorithm-Evolve.spec of Package perl-Algorithm-Evolve

#
# spec file for package perl-Algorithm-Evolve
#
# Copyright (c) 2016 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 http://bugs.opensuse.org/
#


Name:           perl-Algorithm-Evolve
Version:        0.03
Release:        0
%define cpan_name Algorithm-Evolve
Summary:        An extensible and generic framework for executing 
License:        GPL-1.0+ or Artistic-1.0
Group:          Development/Libraries/Perl
Url:            http://search.cpan.org/dist/Algorithm-Evolve/
Source0:        http://www.cpan.org/authors/id/R/RO/ROSULEK/%{cpan_name}-%{version}.tar.gz
BuildArch:      noarch
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildRequires:  perl
BuildRequires:  perl-macros
%{perl_requires}

%description
This module is intended to be a useful tool for quick and easy
implementation of evolutionary algorithms. It aims to be flexible, yet
simple. For this reason, it is not a comprehensive implementation of all
possible evolutionary algorithm configurations. The flexibility of Perl
allows the evolution of any type of object conceivable: a simple string or
array, a deeper structure like a hash of arrays, or even something as
complex as graph object from another CPAN module, etc.

It's also worth mentioning that evolutionary algorithms are generally very
CPU-intensive. There are a great deal of calls to 'rand()' and a lot of
associated floating-point math. If you want a lightning-fast framework,
then searching CPAN at all is probably a bad place to start. However, this
doesn't mean that I've ignored efficiency. The fitness function is often
the biggest bottleneck.

%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

%files -f %{name}.files
%defattr(-,root,root,755)
%doc Changes examples README TODO

%changelog