How to Install and Uninstall perl-Pod-Coverage-TrustPod Package on openSUSE Leap

Last updated: July 08,2024

1. Install "perl-Pod-Coverage-TrustPod" package

This is a short guide on how to install perl-Pod-Coverage-TrustPod on openSUSE Leap

$ sudo zypper refresh $ sudo zypper install perl-Pod-Coverage-TrustPod

2. Uninstall "perl-Pod-Coverage-TrustPod" package

Please follow the steps below to uninstall perl-Pod-Coverage-TrustPod on openSUSE Leap:

$ sudo zypper remove perl-Pod-Coverage-TrustPod

3. Information about the perl-Pod-Coverage-TrustPod package on openSUSE Leap

Information for package perl-Pod-Coverage-TrustPod:
---------------------------------------------------
Repository : Main Repository
Name : perl-Pod-Coverage-TrustPod
Version : 0.100006-bp155.1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 27.7 KiB
Installed : No
Status : not installed
Source package : perl-Pod-Coverage-TrustPod-0.100006-bp155.1.4.src
Upstream URL : https://metacpan.org/release/Pod-Coverage-TrustPod
Summary : Allow a module's pod to contain Pod::Coverage hints
Description :
This is a Pod::Coverage subclass (actually, a subclass of
Pod::Coverage::CountParents) that allows the POD itself to declare certain
symbol names trusted.
Here is a sample Perl module:
package Foo::Bar;
=head1 NAME
Foo::Bar - a bar at which fooes like to drink
=head1 METHODS
=head2 fee
returns the bar tab
=cut
sub fee { ... }
=head2 fie
scoffs at bar tab
=cut
sub fie { ... }
sub foo { ... }
=begin Pod::Coverage
foo
=end Pod::Coverage
=cut
This file would report full coverage, because any non-empty lines inside a
block of POD targeted to Pod::Coverage are treated as 'trustme' patterns.
Leading and trailing whitespace is stripped and the remainder is treated as
a regular expression anchored at both ends.
Remember, anywhere you could use '=begin' and '=end' as above, you could
instead write:
=for Pod::Coverage foo
In some cases, you may wish to make the entire file trusted. The special
pattern '*EVERYTHING*' may be provided to do just this.
Keep in mind that Pod::Coverage::TrustPod sets up exceptions using the
"trust" mechanism rather than the "privacy" mechanism in Pod::Coverage.
This is unlikely ever to matter to you, but it's true.