How to Install and Uninstall perl-ExtUtils-InstallPaths Package on openSuSE Tumbleweed

Last updated: May 18,2024

1. Install "perl-ExtUtils-InstallPaths" package

Please follow the steps below to install perl-ExtUtils-InstallPaths on openSuSE Tumbleweed

$ sudo zypper refresh $ sudo zypper install perl-ExtUtils-InstallPaths

2. Uninstall "perl-ExtUtils-InstallPaths" package

In this section, we are going to explain the necessary steps to uninstall perl-ExtUtils-InstallPaths on openSuSE Tumbleweed:

$ sudo zypper remove perl-ExtUtils-InstallPaths

3. Information about the perl-ExtUtils-InstallPaths package on openSuSE Tumbleweed

Information for package perl-ExtUtils-InstallPaths:
---------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : perl-ExtUtils-InstallPaths
Version : 0.012-1.24
Arch : noarch
Vendor : openSUSE
Installed Size : 42.9 KiB
Installed : No
Status : not installed
Source package : perl-ExtUtils-InstallPaths-0.012-1.24.src
Upstream URL : http://search.cpan.org/dist/ExtUtils-InstallPaths/
Summary : Build.PL install path logic made easy
Description :
This module tries to make install path resolution as easy as possible.
When you want to install a module, it needs to figure out where to install
things. The nutshell version of how this works is that default installation
locations are determined from ExtUtils::Config, and they may be
individually overridden by using the 'install_path' attribute. An
'install_base' attribute lets you specify an alternative installation root
like _/home/foo_ and 'prefix' does something similar in a rather different
(and more complicated) way. 'destdir' lets you specify a temporary
installation directory like _/tmp/install_ in case you want to create
bundled-up installable packages.
The following types are supported by default.
* * lib
Usually pure-Perl module files ending in _.pm_ or _.pod_.
* * arch
"Architecture-dependent" module files, usually produced by compiling XS,
Inline, or similar code.
* * script
Programs written in pure Perl. In order to improve reuse, you may want to
make these as small as possible - put the code into modules whenever
possible.
* * bin
"Architecture-dependent" executable programs, i.e. compiled C code or
something. Pretty rare to see this in a perl distribution, but it happens.
* * bindoc
Documentation for the stuff in 'script' and 'bin'. Usually generated from
the POD in those files. Under Unix, these are manual pages belonging to the
'man1' category. Unless explicitly set, this is only available on platforms
supporting manpages.
* * libdoc
Documentation for the stuff in 'lib' and 'arch'. This is usually generated
from the POD in _.pm_ and _.pod_ files. Under Unix, these are manual pages
belonging to the 'man3' category. Unless explicitly set, this is only
available on platforms supporting manpages.
* * binhtml
This is the same as 'bindoc' above, but applies to HTML documents. Unless
explicitly set, this is only available when perl was configured to do so.
* * libhtml
This is the same as 'libdoc' above, but applies to HTML documents. Unless
explicitly set, this is only available when perl was configured to do so.