File perl-App-Module-Lister.spec of Package perl-App-Module-Lister

#
# spec file for package perl-App-Module-Lister
#
# Copyright (c) 2025 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 App-Module-Lister
Name:           perl-App-Module-Lister
Version:        1.003
Release:        0
License:        Artistic-2.0
Summary:        List the Perl modules in @INC
URL:            https://metacpan.org/release/%{cpan_name}
Source0:        https://cpan.metacpan.org/authors/id/B/BR/BRIANDFOY/%{cpan_name}-%{version}.tar.gz
BuildArch:      noarch
BuildRequires:  perl
BuildRequires:  perl-macros
BuildRequires:  perl(ExtUtils::MakeMaker) >= 6.64
BuildRequires:  perl(Test::More) >= 1
BuildRequires:  perl(version) >= 0.86
%{perl_requires}

%description
This is a program to list all of the Perl modules it finds in '@INC' for a
no-shell web hosting account. It has these explicit design goals:

* * Is a single file FTP upload such that it's ready to run (no archives)

* * Runs as a CGI script

* * Runs on a standard Perl 5.004 system with no non-core modules

* * Does not use CPAN.pm (which can't easly be configured without the
  shell)

If you have a shell account, you should just use 'CPAN.pm''s autobundle
feature.

You do not need to install this module. You just need the '.pm' file. The
rest of the distribution is there to help me give it to other people and
test it.

You might have to modify the shebang line (the first line in the file) to
point to Perl. Your web hoster probably has instructions on what that
should be. As shipped, this program uses the 'env' trick described in
perlrun. If that doesn't work for you, you'll probably see an error like:

	 /usr/bin/env: bad interpreter: No such file or directory

That's similar to the error you'll see if you have the wrong path to
'perl'.

The program searches each entry in '@INC' individually and outputs modules
as it finds them.

%prep
%autosetup  -n %{cpan_name}-%{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 Changes examples SECURITY.md
%license LICENSE

%changelog