Packages / openSUSE Tumbleweed / Source / perl-Dist-CheckConflicts

Source Package: perl-Dist-CheckConflicts (0.110.0-1.5)

Declare version conflicts for your dist

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 module accepts a hash of options passed to its 'use' statement, with these keys being valid: * -conflicts A hashref of conflict specifications, where keys are module names, and values are the last broken version - any version greater than the specified version should work. * -also Additional modules to get conflicts from (potentially recursively). This should generally be a list of modules which use Dist::CheckConflicts, which correspond to the dists that your dist depends on. (In an ideal world, this would be intuited directly from your dependency list, but the dependency list isn't available outside of build time). * -dist The name of the distribution, to make the error message from check_conflicts more user-friendly. The methods listed below are exported by this module into the module that uses it, so you should call these methods on your module, not Dist::CheckConflicts. As an example, this command line can be used to update your modules, after installing the 'Foo' dist (assuming that 'Foo::Conflicts' is the module in the 'Foo' dist which uses Dist::CheckConflicts): perl -MFoo::Conflicts -e'print "$_\n" for map { $_->{package} } Foo::Conflicts->calculate_conflicts' | cpanm As an added bonus, loading your conflicts module will provide warnings at runtime if conflicting modules are detected (regardless of whether they are loaded before or afterwards).

Package information

Homepage
[https://metacpan.org/release/Dist-CheckConflicts]
License
Artistic-1.0 OR GPL-1.0-or-later
Downstream package maintainer
Unknown: not reported in the indexed source

The following binary packages are built from this source package:

Known vulnerabilities

No matching advisories in the tracked sources.

Last synced:

[CVE catalog]

Sources

  • Authoritative source; repository metadata signature verified

    Signature evidence

    tumbleweed-oss-multiarch:4db10cdde3ad82c7e22be35753c9e164b4bdd30f92db4aee17a0d4c94c5f902f

    Repository-signature verification record
    Signed-object SHA-256
    4db10cdde3ad82c7e22be35753c9e164b4bdd30f92db4aee17a0d4c94c5f902f
    Signer fingerprint
    AD485664E901B867051AB15F35A2F86E29B700A4
    Keyring revision
    opensuse-project-signing-key.asc
    SHA-256 b5745739ebfb95b25b8e810f9bcb847fe750ccda598bd85f02f0e974599a6d7e
    Tool and policy
    gpgv (GnuPG) 2.4.9
    openfactory-software-catalog-signature-v1
    Verification time
    Sep 1, 2026
    Repository metadata hash linkage
    Result
    Recorded as verified; digest details unavailable