Files
perl-Scriptalicious/perl-Scriptalicious.spec
2025-08-12 18:17:00 +02:00

76 lines
2.5 KiB
RPMSpec

#
# spec file for package perl-Scriptalicious
#
# 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 Scriptalicious
Name: perl-Scriptalicious
Version: 1.170.0
Release: 0
# 1.17 -> normalize -> 1.170.0
%define cpan_version 1.17
License: Artistic-1.0 OR GPL-1.0-or-later
Summary: Make scripts more delicious to SysAdmins
URL: https://metacpan.org/release/%{cpan_name}
Source0: https://cpan.metacpan.org/authors/id/S/SA/SAMV/%{cpan_name}-%{cpan_version}.tar.gz
Source1: cpanspec.yml
Source100: README.md
BuildArch: noarch
BuildRequires: perl
BuildRequires: perl-macros
BuildRequires: perl(Term::ReadKey)
Requires: perl(Term::ReadKey)
Provides: perl(Scriptalicious) = %{version}
%undefine __perllib_provides
%{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!
%prep
%autosetup -n %{cpan_name}-%{cpan_version}
%build
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 README
%changelog