[Bug 667403] New: Review Request: perl-Dist-CheckConflicts - Declare version conflicts for your dist
bugzilla at redhat.com
bugzilla at redhat.com
Wed Jan 5 14:27:43 UTC 2011
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: Review Request: perl-Dist-CheckConflicts - Declare version conflicts for your dist
https://bugzilla.redhat.com/show_bug.cgi?id=667403
Summary: Review Request: perl-Dist-CheckConflicts - Declare
version conflicts for your dist
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: medium
Component: Package Review
AssignedTo: nobody at fedoraproject.org
ReportedBy: paul at city-fan.org
QAContact: extras-qa at fedoraproject.org
CC: notting at redhat.com, fedora-package-review at redhat.com
Estimated Hours: 0.0
Classification: Fedora
Spec URL:
http://subversion.city-fan.org/repos/cfo-repo/perl-Dist-CheckConflicts/branches/fedora/perl-Dist-CheckConflicts.spec
SRPM URL:
http://www.city-fan.org/~paul/extras/perl-Dist-CheckConflicts/perl-Dist-CheckConflicts-0.02-2.fc15.src.rpm
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.
This package is needed for Package::Stash 0.20.
It is compatible with EPEL-4 once its dependencies List::MoreUtils,
Sub::Exporter and its dependencies Data::OptList, Params::Util, Sub::Install
and Package::Generator are available - I am working on getting these built now.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the package-review
mailing list