File perl-CLI-Framework.spec of Package perl-CLI-Framework

#
# spec file for package perl-CLI-Framework
#
# 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-CLI-Framework
Version:        0.05
Release:        0
%define cpan_name CLI-Framework
Summary:        Build standardized, flexible, testable command-line
License:        Artistic-1.0 or GPL-1.0+
Group:          Development/Libraries/Perl
Url:            http://search.cpan.org/dist/CLI-Framework/
Source0:        http://www.cpan.org/authors/id/K/KE/KERISMAN/%{cpan_name}-%{version}.tar.gz
BuildArch:      noarch
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildRequires:  perl
BuildRequires:  perl-macros
BuildRequires:  perl(Class::Inspector)
BuildRequires:  perl(Exception::Class)
BuildRequires:  perl(Exception::Class::TryCatch)
BuildRequires:  perl(Getopt::Long::Descriptive)
Requires:       perl(Class::Inspector)
Requires:       perl(Exception::Class)
Requires:       perl(Exception::Class::TryCatch)
Requires:       perl(Getopt::Long::Descriptive)
%{perl_requires}

%description
CLI::Framework ("CLIF") provides a framework and conceptual pattern for
building full-featured command line applications. It intends to make this
process simple and consistent. It assumes the responsibility of
implementing details that are common to all command-line applications,
making it possible for new applications adhering to well-defined
conventions to be built without the need to repeatedly write the same
command-line interface code.

For instance, a complete application supporting commands and subcommands,
with options and arguments for the application itself as well as its
commands, can be built by writing concise, understandable code in packages
that are easy to test and maintain. The classes can focus on implementation
of unique aspects essential to the command's purpose without being
concerned with the many details involved in building an interface around
those commands. This methodology for building command-line applications
also establishes a valuable standard for an organization (or an individual
developer).

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

%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 docs examples README

%changelog