File perl-Path-Class-Tiny.spec of Package perl-Path-Class-Tiny
#
# spec file for package perl-Path-Class-Tiny
#
# Copyright (c) 2026 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 Path-Class-Tiny
Name: perl-Path-Class-Tiny
Version: 0.07
Release: 0
License: This is free software, licensed under: The Artistic License 2.0 (GPL Compatible)
Summary: Path::Tiny wrapper for Path::Class compatibility
URL: https://metacpan.org/release/%{cpan_name}
Source0: https://cpan.metacpan.org/authors/id/B/BA/BAREFOOT/%{cpan_name}-%{version}.tar.gz
BuildArch: noarch
BuildRequires: perl
BuildRequires: perl-macros
BuildRequires: perl(Date::Easy::Datetime)
BuildRequires: perl(Module::Runtime)
BuildRequires: perl(Path::Tiny) >= 0.104
BuildRequires: perl(Test::Differences) >= 0.500
BuildRequires: perl(Test::Exception)
BuildRequires: perl(Test::Most) >= 0.25
BuildRequires: perl(parent)
Requires: perl(Date::Easy::Datetime)
Requires: perl(Module::Runtime)
Requires: perl(Path::Tiny) >= 0.104
Recommends: perl(Date::Easy) >= 0.06
%{perl_requires}
%description
What do you do if you started out (Perl) life using Path::Class, but then
later on you switched to Path::Tiny? Well, one thing you could do is
relearn a bunch of things and go change a lot of existing code. Or, another
thing would be to use Path::Class::Tiny instead.
Path::Class::Tiny is a thin(ish) wrapper around Path::Tiny that (mostly)
restores the Path::Class interface. Where the two don't conflict, you can
do it either way. Where they do conflict, you use the Path::Class way.
Except where Path::Class is totally weird, in which case you use the
Path::Tiny way.
Some examples:
%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 CLAUDE.md
%license LICENSE
%changelog