How to Install and Uninstall perl-Module-Signature Package on openSUSE Leap

Last updated: November 23,2024

1. Install "perl-Module-Signature" package

Please follow the guidelines below to install perl-Module-Signature on openSUSE Leap

$ sudo zypper refresh $ sudo zypper install perl-Module-Signature

2. Uninstall "perl-Module-Signature" package

Please follow the guidelines below to uninstall perl-Module-Signature on openSUSE Leap:

$ sudo zypper remove perl-Module-Signature

3. Information about the perl-Module-Signature package on openSUSE Leap

Information for package perl-Module-Signature:
----------------------------------------------
Repository : Main Repository
Name : perl-Module-Signature
Version : 0.88-bp155.1.4
Arch : noarch
Vendor : openSUSE
Installed Size : 135.8 KiB
Installed : No
Status : not installed
Source package : perl-Module-Signature-0.88-bp155.1.4.src
Upstream URL : https://metacpan.org/release/Module-Signature
Summary : Module signature file manipulation
Description :
*Module::Signature* adds cryptographic authentications to CPAN
distributions, via the special _SIGNATURE_ file.
If you are a module user, all you have to do is to remember to run
'cpansign -v' (or just 'cpansign') before issuing 'perl Makefile.PL' or
'perl Build.PL'; that will ensure the distribution has not been tampered
with.
Module authors can easily add the _SIGNATURE_ file to the distribution
tarball; see NOTES below for how to do it as part of 'make dist'.
If you _really_ want to sign a distribution manually, simply add
'SIGNATURE' to _MANIFEST_, then type 'cpansign -s' immediately before 'make
dist'. Be sure to delete the _SIGNATURE_ file afterwards.
Please also see NOTES about _MANIFEST.SKIP_ issues, especially if you are
using *Module::Build* or writing your own _MANIFEST.SKIP_.
Signatures made with Module::Signature prior to version 0.82 used the SHA1
algorithm by default. SHA1 is now considered broken, and therefore module
authors are strongly encouraged to regenerate their _SIGNATURE_ files.
Users verifying old SHA1 signature files will receive a warning.