libdist-checkconflicts-perl 0.09-1 source package in Ubuntu
Changelog
libdist-checkconflicts-perl (0.09-1) unstable; urgency=low * Team upload. [ Salvatore Bonaccorso ] * Change Vcs-Git to canonical URI (git://anonscm.debian.org) * Change search.cpan.org based URIs to metacpan.org based URIs [ gregor herrmann ] * New upstream release. * Update (build) dependencies. * Update years of upstream copyright. * Declare compliance with Debian Policy 3.9.4. -- gregor herrmann <email address hidden> Sun, 22 Sep 2013 19:23:40 +0200
Upload details
- Uploaded by:
- Debian Perl Group
- Uploaded to:
- Sid
- Original maintainer:
- Debian Perl Group
- Architectures:
- all
- Section:
- misc
- Urgency:
- Low Urgency
See full publishing history Publishing
| Series | Published | Component | Section |
|---|
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| libdist-checkconflicts-perl_0.09-1.dsc | 2.2 KiB | 5ea9a9760497e4404930f2fc1f2500895ff75fe9feba270b6297c686200f06ca |
| libdist-checkconflicts-perl_0.09.orig.tar.gz | 18.5 KiB | a0a238746b4f4605e96fd9852d55cf3b8dbbde01981b49a08e3b3858c2cc02ed |
| libdist-checkconflicts-perl_0.09-1.debian.tar.gz | 2.0 KiB | f978f04ae9f4c4277e9b024463caaaf0876d243d28bebef464b7d14d45aa520d |
Available diffs
- diff from 0.02-1 to 0.09-1 (15.1 KiB)
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.
