How to Install and Uninstall libdist-checkconflicts-perl Package on Ubuntu 20.10 (Groovy Gorilla)

Last updated: December 24,2024

1. Install "libdist-checkconflicts-perl" package

Please follow the guidance below to install libdist-checkconflicts-perl on Ubuntu 20.10 (Groovy Gorilla)

$ sudo apt update $ sudo apt install libdist-checkconflicts-perl

2. Uninstall "libdist-checkconflicts-perl" package

This guide let you learn how to uninstall libdist-checkconflicts-perl on Ubuntu 20.10 (Groovy Gorilla):

$ sudo apt remove libdist-checkconflicts-perl $ sudo apt autoclean && sudo apt autoremove

3. Information about the libdist-checkconflicts-perl package on Ubuntu 20.10 (Groovy Gorilla)

Package: libdist-checkconflicts-perl
Architecture: all
Version: 0.11-1
Priority: optional
Section: universe/perl
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Debian Perl Group
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 55
Depends: perl, libmodule-runtime-perl (>= 0.009)
Filename: pool/universe/libd/libdist-checkconflicts-perl/libdist-checkconflicts-perl_0.11-1_all.deb
Size: 10194
MD5sum: 499b02c5cecb0b34a1c2f9173c1b1deb
SHA1: 65b76a0e30e2e6e79fdfa29a78b878b3c7026985
SHA256: 64b8542c9ab9f0bffdcc7e5430b62f307e9deb78ffc4e7527679204ebad4f84c
SHA512: 4859293d4b68949bde20a0301b3794fdf56471f60183953b4548fb3063fdabc5273b3b0c1c8e9ef9eaf28379384e7d3684c96a5a760075e5715aaa27fa274c5b
Homepage: https://metacpan.org/release/Dist-CheckConflicts
Description-en: 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.
Description-md5: 3ed68cbbfaa3fbc4f2e4e4db8290e3f7
Task: ubuntukylin-desktop