| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103 |
- Summary: Declare version conflicts for your dist
- Name: perl-Dist-CheckConflicts
- Version: 0.11
- Release: 2%{?_dist_release}
- Group: programming
- Vendor: Project Vine
- Distribution: Vine Linux
- License: GPL+ or Artistic
- URL: https://metacpan.org/pod/Dist::CheckConflicts
- Source0: https://cpan.metacpan.org/authors/id/D/DO/DOY/Dist-CheckConflicts-%{version}.tar.gz
- BuildArch: noarch
- BuildRequires: perl(Carp)
- BuildRequires: perl(ExtUtils::MakeMaker)
- BuildRequires: perl(IPC::Open3)
- BuildRequires: perl(List::MoreUtils)
- BuildRequires: perl(Module::Runtime)
- BuildRequires: perl(Pod::Coverage::TrustPod)
- BuildRequires: perl(Sub::Exporter)
- BuildRequires: perl(Test::EOL)
- BuildRequires: perl(Test::Fatal)
- BuildRequires: perl(Test::More)
- BuildRequires: perl(Test::NoTabs)
- BuildRequires: perl(Test::Pod)
- BuildRequires: perl(Test::Pod::Coverage)
- Requires: perl >= 2:5.34.0
- %description
- One shortcoming of the CPAN clients that currently exist is that they have no
- way of specifying conflicting downstream dependencies of modules. This module
- attempts to work around this issue by allowing you to specify conflicting
- versions of modules separately, and deal with them after the module is done
- installing.
- For instance, say you have a module Foo, and some other module Bar uses Foo. If
- Foo were to change its API in a non-backwards-compatible way, this would cause
- Bar to break until it is updated to use the new API. Foo can't just depend on
- the fixed version of Bar, because this will cause a circular dependency
- (because Bar is already depending on Foo), and this doesn't express intent
- properly anyway - Foo doesn't use Bar at all. The ideal solution would be for
- there to be a way to specify conflicting versions of modules in a way that would
- let CPAN clients update conflicting modules automatically after an existing
- module is upgraded, but until that happens, this module will allow users to do
- this manually.
- %prep
- %setup -q -n Dist-CheckConflicts-%{version}
- %build
- perl Makefile.PL INSTALLDIRS=vendor NO_PACKLIST=1 NO_PERLLOCAL=1
- make %{?_smp_mflags}
- %install
- rm -rf %{buildroot}
- make pure_install DESTDIR=%{buildroot}
- find %{buildroot} -depth -type d -exec rmdir {} \; 2>/dev/null
- %{_fixperms} %{buildroot}
- %check
- make test RELEASE_TESTING=1
- %clean
- rm -rf %{buildroot}
- %files
- %doc Changes LICENSE README
- %{perl_vendorlib}/Dist/
- %{_mandir}/man3/Dist::CheckConflicts.3pm*
- %changelog
- * Sun Nov 21 2021 Tomohiro "Tomo-p" KATO <tomop@teamgedoh.net> 0.11-2
- - rebuilt with perl-5.34.0.
- * Fri Dec 19 2014 Ryoichi INAGAKI <ryo1@toki.waseda.jp> 0.11-1
- - updated to 0.11
- - built with perl 5.16.3
- - added BR: perl(Module::Runtime)
- * Mon Mar 05 2012 MATSUBAYASHI Kohji <shaolin@vinelinux.org> - 0.02-1
- - initial build for Vine Linux
- * Wed Jan 11 2012 Paul Howarth <paul@city-fan.org> - 0.02-5
- - Pod::Coverage::TrustPod now available in all supported releases
- - BR: perl(Carp)
- * Tue Jul 19 2011 Petr Sabata <contyk@redhat.com> - 0.02-4
- - Perl mass rebuild
- * Tue Feb 08 2011 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 0.02-3
- - Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild
- * Wed Jan 5 2011 Paul Howarth <paul@city-fan.org> - 0.02-2
- - Sanitize for Fedora submission
- * Tue Jan 4 2011 Paul Howarth <paul@city-fan.org> - 0.02-1
- - Initial RPM version
|
