How to Install and Uninstall perl-PadWalker Package on openSuSE Tumbleweed
Last updated: December 23,2024
1. Install "perl-PadWalker" package
Please follow the instructions below to install perl-PadWalker on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
perl-PadWalker
Copied
2. Uninstall "perl-PadWalker" package
Please follow the step by step instructions below to uninstall perl-PadWalker on openSuSE Tumbleweed:
$
sudo zypper remove
perl-PadWalker
Copied
3. Information about the perl-PadWalker package on openSuSE Tumbleweed
Information for package perl-PadWalker:
---------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-PadWalker
Version : 2.5-1.19
Arch : x86_64
Vendor : openSUSE
Installed Size : 43.7 KiB
Installed : No
Status : not installed
Source package : perl-PadWalker-2.5-1.19.src
Upstream URL : https://metacpan.org/release/PadWalker
Summary : Play with other peoples' lexical variables
Description :
PadWalker is a module which allows you to inspect (and even change!)
lexical variables in any subroutine which called you. It will only show
those variables which are in scope at the point of the call.
PadWalker is particularly useful for debugging. It's even used by Perl's
built-in debugger. (It can also be used for evil, of course.)
I wouldn't recommend using PadWalker directly in production code, but it's
your call. Some of the modules that use PadWalker internally are certainly
safe for and useful in production.
---------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-PadWalker
Version : 2.5-1.19
Arch : x86_64
Vendor : openSUSE
Installed Size : 43.7 KiB
Installed : No
Status : not installed
Source package : perl-PadWalker-2.5-1.19.src
Upstream URL : https://metacpan.org/release/PadWalker
Summary : Play with other peoples' lexical variables
Description :
PadWalker is a module which allows you to inspect (and even change!)
lexical variables in any subroutine which called you. It will only show
those variables which are in scope at the point of the call.
PadWalker is particularly useful for debugging. It's even used by Perl's
built-in debugger. (It can also be used for evil, of course.)
I wouldn't recommend using PadWalker directly in production code, but it's
your call. Some of the modules that use PadWalker internally are certainly
safe for and useful in production.