perl-Scriptalicious/perl-Scriptalicious.spec

#
# spec file for package perl-Scriptalicious
#
# 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/
#

# norootforbuild


Name:           perl-Scriptalicious
%define cpan_name Scriptalicious
Summary:        Make scripts more delicious to SysAdmins
Url:            http://search.cpan.org/perldoc?Scriptalicious
Group:          Development/Libraries/Perl
License:        Artistic License
Version:        1.16
Release:        1
Source:         %{cpan_name}-%{version}.tar.bz2
BuildRequires:  perl-macros
BuildRequires:  perl(YAML)
BuildRequires:  perl(Term::ReadKey)
Requires:       perl(YAML)
Requires:       perl(Term::ReadKey)
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
%{perl_requires}

%description
This module helps you write scripts that conform to best common practices,
quickly. Just include the above as a template, and your script will accept all
of the options that are included in the manual page, as well as summarising
them when you use the -h option.

(Unfortunately, it is not possible to have a `use' dependency automatically add
structure to your POD yet, so you have to include the above manually. If you
want your help message and Perldoc to be meaningful, that is.)

Shortcuts are provided to help you abort or die with various error conditions;
all of which print the name of the program running (taken from $0 if not
passed). The motive for this is that "small" scripts tend to just get written
and forgotten; so, when you have a larger system that is built out of lots of
these pieces it is sometimes guesswork figuring out which script a printed
message comes from!


Author:
-------
    Sam Vilain, samv@cpan.org


%prep
%setup -n %{cpan_name}-%{version}

%build
perl Makefile.PL 
make %{?jobs:-j%jobs}

%check
make test

%install
%perl_make_install
%perl_process_packlist
%perl_gen_filelist

%clean
rm -rf %{buildroot}

%files -f %{name}.files 
%defattr(-, root, root)
%doc Changes.pod README MANIFEST

%changelog