public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/perl-File-CheckTree] epel10.3: Import
Date: Wed, 26 Aug 2026 11:12:01 GMT [thread overview]
Message-ID: <178774272179.1.3718545899573129458.rpms-perl-File-CheckTree-c15287ac6143@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/perl-File-CheckTree
Branch : epel10.3
Commit : c15287ac6143bc10ab30132d6f698dd3a4379600
Author : Petr Písař <ppisar@redhat.com>
Date : 2013-03-05T15:35:51+01:00
Stats : +65/-0 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/perl-File-CheckTree/c/c15287ac6143bc10ab30132d6f698dd3a4379600?branch=epel10.3
Log:
Import
---
diff --git a/.gitignore b/.gitignore
index e69de29..2747f5e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/File-CheckTree-4.42.tar.gz
diff --git a/perl-File-CheckTree.spec b/perl-File-CheckTree.spec
new file mode 100644
index 0000000..849be92
--- /dev/null
+++ b/perl-File-CheckTree.spec
@@ -0,0 +1,63 @@
+Name: perl-File-CheckTree
+Version: 4.42
+Release: 1%{?dist}
+Summary: Run many file-test checks on a tree
+License: GPL+ or Artistic
+Group: Development/Libraries
+URL: http://search.cpan.org/dist/File-CheckTree/
+Source0: http://www.cpan.org/authors/id/R/RJ/RJBS/File-CheckTree-%{version}.tar.gz
+BuildArch: noarch
+BuildRequires: perl
+BuildRequires: perl(ExtUtils::MakeMaker) >= 6.30
+BuildRequires: perl(strict)
+BuildRequires: perl(warnings)
+# Run-time:
+BuildRequires: perl(Cwd)
+%if 0%(perl -e 'print $] > 5.017')
+BuildRequires: perl(deprecated)
+%endif
+BuildRequires: perl(Exporter)
+BuildRequires: perl(File::Spec)
+BuildRequires: perl(if)
+# Tests:
+BuildRequires: perl(overload)
+BuildRequires: perl(Test::More)
+Requires: perl(:MODULE_COMPAT_%(eval "`perl -V:version`"; echo $version))
+%if 0%(perl -e 'print $] > 5.017')
+Requires: perl(deprecated)
+%endif
+
+%description
+File::CheckTree::validate() routine takes a single multi-line string
+consisting of directives, each containing a file name plus a file test to try
+on it. (The file test may also be a "cd", causing subsequent relative file
+names to be interpreted relative to that directory.) After the file test you
+may put || die to make it a fatal error if the file test fails. The default is
+|| warn. The file test may optionally have a "!' prepended to test for the
+opposite condition. If you do a cd and then list some relative file names, you
+may want to indent them slightly for readability. If you supply your own die()
+or warn() message, you can use $file to interpolate the file name.
+
+%prep
+%setup -q -n File-CheckTree-%{version}
+
+%build
+perl Makefile.PL INSTALLDIRS=vendor
+make %{?_smp_mflags}
+
+%install
+make pure_install DESTDIR=$RPM_BUILD_ROOT
+find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
+%{_fixperms} $RPM_BUILD_ROOT/*
+
+%check
+make test
+
+%files
+%doc Changes LICENSE README
+%{perl_vendorlib}/*
+%{_mandir}/man3/*
+
+%changelog
+* Fri Feb 08 2013 Petr Pisar <ppisar@redhat.com> 4.42-1
+- Specfile autogenerated by cpanspec 1.78.
diff --git a/sources b/sources
index e69de29..e0d6c3e 100644
--- a/sources
+++ b/sources
@@ -0,0 +1 @@
+3e374bdb0dcc1fa5869b938bdea0eb79 File-CheckTree-4.42.tar.gz
reply other threads:[~2026-08-26 11:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178774272179.1.3718545899573129458.rpms-perl-File-CheckTree-c15287ac6143@fedoraproject.org \
--to=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox