libdist-checkconflicts-perl 0.11-1 source package in Ubuntu


libdist-checkconflicts-perl (0.11-1) unstable; urgency=medium

  * Team upload.
  * New upstream release.
  * Strip trailing slash from metacpan URLs.
  * Update years of upstream copyright.
  * Drop (build) dependency on liblist-moreutils-perl.

 -- gregor herrmann <email address hidden>  Mon, 05 May 2014 22:23:05 +0200

Upload details

Uploaded by:
Debian Perl Group on 2014-05-06
Uploaded to:
Original maintainer:
Debian Perl Group
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Focal release on 2019-10-18 universe misc
Eoan release on 2019-04-18 universe misc
Disco release on 2018-10-30 universe misc
Cosmic release on 2018-05-01 universe misc
Bionic release on 2017-10-24 universe misc
Artful release on 2017-04-20 universe misc
Xenial release on 2016-04-08 universe misc


Utopic: [FULLYBUILT] i386


File Size SHA-256 Checksum
libdist-checkconflicts-perl_0.11-1.dsc 2.3 KiB 0b798da136b8cd154f009a20a7c8ea092f7ac83127b9a171d948a8758fabbca0
libdist-checkconflicts-perl_0.11.orig.tar.gz 19.5 KiB ea844b9686c94d666d9d444321d764490b2cde2f985c4165b4c2c77665caedc4
libdist-checkconflicts-perl_0.11-1.debian.tar.xz 2.1 KiB 393e6883188c7f523ea35bd3aaed03780a9adb1c45f5ccc6e047c357a2199742

Available diffs

No changes file available.

Binary packages built by this source

libdist-checkconflicts-perl: module for declaring version conflicts for a distribution

 One shortcoming of the CPAN clients that currently exist is that they have no
 way of specifying conflicting downstream dependencies of modules.
 Dist::CheckConflicts 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.