File perl-Test-File-Cmp.spec of Package perl-Test-File-Cmp
#
# spec file for package perl-Test-File-Cmp
#
# 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 Test-File-Cmp
Name: perl-Test-File-Cmp
Version: 0.06
Release: 0
License: Artistic-1.0 OR GPL-1.0-or-later
Summary: Test routine for file comparison independent of CRLF or LF line endings
URL: https://metacpan.org/release/%{cpan_name}
Source0: https://cpan.metacpan.org/authors/id/A/AA/AAHAZRED/%{cpan_name}-%{version}.tar.gz
BuildArch: noarch
BuildRequires: perl
BuildRequires: perl-macros
%{perl_requires}
%description
For testing files and their contents, Test::File::Contents is a good
choice. But I missed one feature: what if you need to run tests on both
systems, Windows and Linux, *and* the "expected" files might be created on
one or the other system and you don't know that in advance? Then there are
ugly problems with line endings when comparing the contents of two files,
and the 'encoding' argument does not really resolve this.
For this situation I have created a file comparison function provided by
this module, description see below.
%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 README
%license LICENSE
%changelog