#
# spec file for package perl-File-Remote
#
# 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 File-Remote
Name:           perl-File-Remote
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:        Read/write/edit remote files transparently
URL:            https://metacpan.org/release/%{cpan_name}
Source0:        https://cpan.metacpan.org/authors/id/N/NW/NWIGER/%{cpan_name}-%{cpan_version}.tar.gz
Source1:        cpanspec.yml
Source100:      README.md
BuildArch:      noarch
BuildRequires:  perl
BuildRequires:  perl-macros
Provides:       perl(File::Remote) = %{version}
%undefine       __perllib_provides
%{perl_requires}

%description
This module takes care of dealing with files regardless of whether they're
local or remote. It allows you to create and edit files without having to
worry about their physical location on the network. If a file passed into a
function is of the form 'host:/path/to/file', then 'File::Remote' uses
rsh/rcp (or ssh/scp, depending on how you configure it) to edit the file
remotely. Otherwise, it assumes the file is local and passes calls directly
through to Perl's core functions.

The nice thing about this module is that you can use it for _all_ your file
calls, since it handles both remote and local files transparently. This
means you don't have to put a whole bunch of checks for remote files in
your code. Plus, if you use the function-oriented interface along with the
':replace' tag, you can actually redefine the Perl builtin file functions.
This means that your existing Perl scripts can automatically handle remote
files with no re-engineering(!).

%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 Changes README Todo

%changelog