rpms/perl-Dist-CheckConflicts
7
0
Fork 0
Code Issues Pull Requests Releases Activity
7bd40a0d44
perl-Dist-CheckConflicts/perl-Dist-CheckConflicts.spec

192 lines
6.9 KiB
RPMSpec
Raw Normal View History

Initial import of perl-Dist-CheckConflicts-0.02-2 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.
2011-01-06 14:55:11 +00:00
# We need to patch the test suite if we have an old version of Test::More
Update to 0.06 - New upstream release 0.06 - Add optional runtime conflict warnings - Require 5.8.1, clean up a few things and add a few more tests - Use Exporter instead of Sub::Exporter - Update patch for building with Test::More < 0.88 - Drop patch for building with old ExtUtils::MakeMaker, no longer needed - Don't need to remove empty directories from the buildroot
2013-06-22 21:02:50 +00:00
%global old_test_more %(perl -MTest::More -e 'print (($Test::More::VERSION < 0.88) ? 1 : 0);' 2>/dev/null || echo 0)
Control extra test by _without_perl_Dist_CheckConflicts_enables_extra_test
2017-12-06 15:51:26 +00:00
# Run extra test
%if 0%{?fedora}
%bcond_without perl_Dist_CheckConflicts_enables_extra_test
%else
%bcond_with perl_Dist_CheckConflicts_enables_extra_test
%endif
Initial import of perl-Dist-CheckConflicts-0.02-2 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.
2011-01-06 14:55:11 +00:00
Name: perl-Dist-CheckConflicts
Update to 0.11 - New upstream release 0.11 - Drop the dep on List::MoreUtils (https://github.com/doy/dist-checkconflicts/pull/8) - Update patch for building with Test::More < 0.88 - Don't try to run the extra tests for EPEL builds
2014-04-03 19:52:35 +00:00
Version: 0.11
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
2017-07-27 03:40:43 +00:00
Release: 10%{?dist}
Initial import of perl-Dist-CheckConflicts-0.02-2 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.
2011-01-06 14:55:11 +00:00
Summary: Declare version conflicts for your dist
Group: Development/Libraries
License: GPL+ or Artistic
URL: http://search.cpan.org/dist/Dist-CheckConflicts/
Source0: http://search.cpan.org/CPAN/authors/id/D/DO/DOY/Dist-CheckConflicts-%{version}.tar.gz
Update to 0.11 - New upstream release 0.11 - Drop the dep on List::MoreUtils (https://github.com/doy/dist-checkconflicts/pull/8) - Update patch for building with Test::More < 0.88 - Don't try to run the extra tests for EPEL builds
2014-04-03 19:52:35 +00:00
Patch0: Dist-CheckConflicts-0.11-old-Test::More.patch
Pod::Coverage::TrustPod now available in all supported releases
2012-01-11 14:36:00 +00:00
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(id -nu)
Initial import of perl-Dist-CheckConflicts-0.02-2 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.
2011-01-06 14:55:11 +00:00
BuildArch: noarch
Update to 0.08 - New upstream release 0.08 - Instead of silently ignoring conflicts that do not compile, issue a conflict warning (CPAN RT#75486) - BR: perl(Module::Runtime) - Classify buildreqs by usage - Explicitly run the extra tests
2013-07-10 15:11:51 +00:00
# Module Build
Mandatory Perl build-requires added <https://fedoraproject.org/wiki/Changes/Build_Root_Without_Perl>
2016-06-24 08:41:40 +00:00
BuildRequires: perl-generators
Update to 0.08 - New upstream release 0.08 - Instead of silently ignoring conflicts that do not compile, issue a conflict warning (CPAN RT#75486) - BR: perl(Module::Runtime) - Classify buildreqs by usage - Explicitly run the extra tests
2013-07-10 15:11:51 +00:00
BuildRequires: perl(ExtUtils::MakeMaker) >= 6.30
# Module
Update to 0.06 - New upstream release 0.06 - Add optional runtime conflict warnings - Require 5.8.1, clean up a few things and add a few more tests - Use Exporter instead of Sub::Exporter - Update patch for building with Test::More < 0.88 - Drop patch for building with old ExtUtils::MakeMaker, no longer needed - Don't need to remove empty directories from the buildroot
2013-06-22 21:02:50 +00:00
BuildRequires: perl(base)
Pod::Coverage::TrustPod now available in all supported releases
2012-01-11 14:36:00 +00:00
BuildRequires: perl(Carp)
Update to 0.06 - New upstream release 0.06 - Add optional runtime conflict warnings - Require 5.8.1, clean up a few things and add a few more tests - Use Exporter instead of Sub::Exporter - Update patch for building with Test::More < 0.88 - Drop patch for building with old ExtUtils::MakeMaker, no longer needed - Don't need to remove empty directories from the buildroot
2013-06-22 21:02:50 +00:00
BuildRequires: perl(Exporter)
Update to 0.10 - New upstream release 0.10 - We need Module::Runtime 0.009 for module_notional_filename (#6) - Update patch for building with Test::More < 0.88 - Drop %defattr, redundant since rpm 4.4
2013-12-18 11:32:13 +00:00
BuildRequires: perl(Module::Runtime) >= 0.009
Update to 0.08 - New upstream release 0.08 - Instead of silently ignoring conflicts that do not compile, issue a conflict warning (CPAN RT#75486) - BR: perl(Module::Runtime) - Classify buildreqs by usage - Explicitly run the extra tests
2013-07-10 15:11:51 +00:00
BuildRequires: perl(strict)
BuildRequires: perl(warnings)
# Test Suite
Update to 0.10 - New upstream release 0.10 - We need Module::Runtime 0.009 for module_notional_filename (#6) - Update patch for building with Test::More < 0.88 - Drop %defattr, redundant since rpm 4.4
2013-12-18 11:32:13 +00:00
BuildRequires: perl(File::Spec)
BuildRequires: perl(IO::Handle)
BuildRequires: perl(IPC::Open3)
Update to 0.06 - New upstream release 0.06 - Add optional runtime conflict warnings - Require 5.8.1, clean up a few things and add a few more tests - Use Exporter instead of Sub::Exporter - Update patch for building with Test::More < 0.88 - Drop patch for building with old ExtUtils::MakeMaker, no longer needed - Don't need to remove empty directories from the buildroot
2013-06-22 21:02:50 +00:00
BuildRequires: perl(lib)
Update to 0.08 - New upstream release 0.08 - Instead of silently ignoring conflicts that do not compile, issue a conflict warning (CPAN RT#75486) - BR: perl(Module::Runtime) - Classify buildreqs by usage - Explicitly run the extra tests
2013-07-10 15:11:51 +00:00
BuildRequires: perl(Test::Fatal)
BuildRequires: perl(Test::More) >= 0.47
# Extra Tests
Control extra test by _without_perl_Dist_CheckConflicts_enables_extra_test
2017-12-06 15:51:26 +00:00
%if %{with perl_Dist_CheckConflicts_enables_extra_test}
Initial import of perl-Dist-CheckConflicts-0.02-2 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.
2011-01-06 14:55:11 +00:00
BuildRequires: perl(Pod::Coverage::TrustPod)
BuildRequires: perl(Test::EOL)
BuildRequires: perl(Test::NoTabs)
Specify version requirements for extra test modules
2014-04-03 20:03:20 +00:00
BuildRequires: perl(Test::Pod) >= 1.41
BuildRequires: perl(Test::Pod::Coverage) >= 1.08
Update to 0.11 - New upstream release 0.11 - Drop the dep on List::MoreUtils (https://github.com/doy/dist-checkconflicts/pull/8) - Update patch for building with Test::More < 0.88 - Don't try to run the extra tests for EPEL builds
2014-04-03 19:52:35 +00:00
%endif
Update to 0.08 - New upstream release 0.08 - Instead of silently ignoring conflicts that do not compile, issue a conflict warning (CPAN RT#75486) - BR: perl(Module::Runtime) - Classify buildreqs by usage - Explicitly run the extra tests
2013-07-10 15:11:51 +00:00
# Runtime
Pod::Coverage::TrustPod now available in all supported releases
2012-01-11 14:36:00 +00:00
Requires: perl(:MODULE_COMPAT_%(eval "`perl -V:version`"; echo $version))
Initial import of perl-Dist-CheckConflicts-0.02-2 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.
2011-01-06 14:55:11 +00:00
%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}
# Test suite needs patching if we have Test::More < 0.88
%if %{old_test_more}
Update to 0.08 - New upstream release 0.08 - Instead of silently ignoring conflicts that do not compile, issue a conflict warning (CPAN RT#75486) - BR: perl(Module::Runtime) - Classify buildreqs by usage - Explicitly run the extra tests
2013-07-10 15:11:51 +00:00
%patch0
Initial import of perl-Dist-CheckConflicts-0.02-2 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.
2011-01-06 14:55:11 +00:00
%endif
%build
perl Makefile.PL INSTALLDIRS=vendor
make %{?_smp_mflags}
%install
rm -rf %{buildroot}
make pure_install DESTDIR=%{buildroot}
find %{buildroot} -type f -name .packlist -exec rm -f {} \;
%{_fixperms} %{buildroot}
%check
Update to 0.08 - New upstream release 0.08 - Instead of silently ignoring conflicts that do not compile, issue a conflict warning (CPAN RT#75486) - BR: perl(Module::Runtime) - Classify buildreqs by usage - Explicitly run the extra tests
2013-07-10 15:11:51 +00:00
make test
Control extra test by _without_perl_Dist_CheckConflicts_enables_extra_test
2017-12-06 15:51:26 +00:00
%if %{with perl_Dist_CheckConflicts_enables_extra_test}
Update to 0.08 - New upstream release 0.08 - Instead of silently ignoring conflicts that do not compile, issue a conflict warning (CPAN RT#75486) - BR: perl(Module::Runtime) - Classify buildreqs by usage - Explicitly run the extra tests
2013-07-10 15:11:51 +00:00
make test TEST_FILES="$(echo $(find xt/ -name '*.t'))"
Update to 0.11 - New upstream release 0.11 - Drop the dep on List::MoreUtils (https://github.com/doy/dist-checkconflicts/pull/8) - Update patch for building with Test::More < 0.88 - Don't try to run the extra tests for EPEL builds
2014-04-03 19:52:35 +00:00
%endif
Initial import of perl-Dist-CheckConflicts-0.02-2 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.
2011-01-06 14:55:11 +00:00
%clean
rm -rf %{buildroot}
%files
%doc Changes LICENSE README
%{perl_vendorlib}/Dist/
%{_mandir}/man3/Dist::CheckConflicts.3pm*
%changelog
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
2017-07-27 03:40:43 +00:00
* Thu Jul 27 2017 Fedora Release Engineering <releng@fedoraproject.org> - 0.11-10
- Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild
Perl 5.26 rebuild
2017-06-05 11:02:37 +00:00
* Mon Jun 05 2017 Jitka Plesnikova <jplesnik@redhat.com> - 0.11-9
- Perl 5.26 rebuild
- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
2017-02-11 02:49:31 +00:00
* Sat Feb 11 2017 Fedora Release Engineering <releng@fedoraproject.org> - 0.11-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild
Perl 5.24 rebuild
2016-05-15 22:13:10 +00:00
* Sun May 15 2016 Jitka Plesnikova <jplesnik@redhat.com> - 0.11-7
- Perl 5.24 rebuild
- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild
2016-02-04 13:24:37 +00:00
* Thu Feb 04 2016 Fedora Release Engineering <releng@fedoraproject.org> - 0.11-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild
- Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild
2015-06-18 02:49:43 +00:00
* Thu Jun 18 2015 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 0.11-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild
Perl 5.22 rebuild
2015-06-06 08:45:37 +00:00
* Sat Jun 06 2015 Jitka Plesnikova <jplesnik@redhat.com> - 0.11-4
- Perl 5.22 rebuild
Perl 5.20 rebuild
2014-08-29 00:46:43 +00:00
* Fri Aug 29 2014 Jitka Plesnikova <jplesnik@redhat.com> - 0.11-3
- Perl 5.20 rebuild
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
2014-06-07 03:40:15 +00:00
* Sat Jun 07 2014 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 0.11-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
Update to 0.11 - New upstream release 0.11 - Drop the dep on List::MoreUtils (https://github.com/doy/dist-checkconflicts/pull/8) - Update patch for building with Test::More < 0.88 - Don't try to run the extra tests for EPEL builds
2014-04-03 19:52:35 +00:00
* Thu Apr 3 2014 Paul Howarth <paul@city-fan.org> - 0.11-1
- Update to 0.11
- Drop the dep on List::MoreUtils
(https://github.com/doy/dist-checkconflicts/pull/8)
- Update patch for building with Test::More < 0.88
- Don't try to run the extra tests for EPEL builds
Specify version requirements for extra test modules
2014-04-03 20:03:20 +00:00
- Specify version requirements for extra test modules
Update to 0.11 - New upstream release 0.11 - Drop the dep on List::MoreUtils (https://github.com/doy/dist-checkconflicts/pull/8) - Update patch for building with Test::More < 0.88 - Don't try to run the extra tests for EPEL builds
2014-04-03 19:52:35 +00:00
Update to 0.10 - New upstream release 0.10 - We need Module::Runtime 0.009 for module_notional_filename (#6) - Update patch for building with Test::More < 0.88 - Drop %defattr, redundant since rpm 4.4
2013-12-18 11:32:13 +00:00
* Wed Dec 18 2013 Paul Howarth <paul@city-fan.org> - 0.10-1
- Update to 0.10
- We need Module::Runtime 0.009 for module_notional_filename (#6)
- Update patch for building with Test::More < 0.88
- Drop %%defattr, redundant since rpm 4.4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
2013-08-03 20:14:51 +00:00
* Sat Aug 03 2013 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 0.09-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_20_Mass_Rebuild
Perl 5.18 rebuild
2013-07-26 19:36:03 +00:00
* Fri Jul 26 2013 Petr Pisar <ppisar@redhat.com> - 0.09-2
- Perl 5.18 rebuild
Update to 0.09 - New upstream release 0.09 - Support Perl 5.6.x
2013-07-22 08:53:35 +00:00
* Mon Jul 22 2013 Paul Howarth <paul@city-fan.org> - 0.09-1
- Update to 0.09
- Support Perl 5.6.x
Update to 0.08 - New upstream release 0.08 - Instead of silently ignoring conflicts that do not compile, issue a conflict warning (CPAN RT#75486) - BR: perl(Module::Runtime) - Classify buildreqs by usage - Explicitly run the extra tests
2013-07-10 15:11:51 +00:00
* Wed Jul 10 2013 Paul Howarth <paul@city-fan.org> - 0.08-1
- Update to 0.08
- Instead of silently ignoring conflicts that do not compile, issue a
conflict warning (CPAN RT#75486)
- BR: perl(Module::Runtime)
- Classify buildreqs by usage
- Explicitly run the extra tests
Update to 0.06 - New upstream release 0.06 - Add optional runtime conflict warnings - Require 5.8.1, clean up a few things and add a few more tests - Use Exporter instead of Sub::Exporter - Update patch for building with Test::More < 0.88 - Drop patch for building with old ExtUtils::MakeMaker, no longer needed - Don't need to remove empty directories from the buildroot
2013-06-22 21:02:50 +00:00
* Sat Jun 22 2013 Paul Howarth <paul@city-fan.org> - 0.06-1
- Update to 0.06
- Add optional runtime conflict warnings
- Require 5.8.1, clean up a few things and add a few more tests
- Use Exporter instead of Sub::Exporter
- Update patch for building with Test::More < 0.88
- Drop patch for building with old ExtUtils::MakeMaker, no longer needed
- Don't need to remove empty directories from the buildroot
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
2013-02-14 12:05:26 +00:00
* Thu Feb 14 2013 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 0.02-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_19_Mass_Rebuild
- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
2012-07-20 14:55:42 +00:00
* Fri Jul 20 2012 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 0.02-7
- Rebuilt for https://fedoraproject.org/wiki/Fedora_18_Mass_Rebuild
Perl 5.16 rebuild
2012-06-19 08:24:58 +00:00
* Tue Jun 19 2012 Petr Pisar <ppisar@redhat.com> - 0.02-6
- Perl 5.16 rebuild
Pod::Coverage::TrustPod now available in all supported releases
2012-01-11 14:36:00 +00:00
* 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)
Perl mass rebuild
2011-07-19 15:35:18 +00:00
* Tue Jul 19 2011 Petr Sabata <contyk@redhat.com> - 0.02-4
- Perl mass rebuild
- Rebuilt for https://fedoraproject.org/wiki/Fedora_15_Mass_Rebuild
2011-02-08 21:38:35 +00:00
* 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
Initial import of perl-Dist-CheckConflicts-0.02-2 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.
2011-01-06 14:55:11 +00:00
* 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
Reference in New Issue Copy Permalink