How to Install and Uninstall perl-File-ShareDir Package on openSUSE Leap

Last updated: November 07,2024

1. Install "perl-File-ShareDir" package

Please follow the guidance below to install perl-File-ShareDir on openSUSE Leap

$ sudo zypper refresh $ sudo zypper install perl-File-ShareDir

2. Uninstall "perl-File-ShareDir" package

Here is a brief guide to show you how to uninstall perl-File-ShareDir on openSUSE Leap:

$ sudo zypper remove perl-File-ShareDir

3. Information about the perl-File-ShareDir package on openSUSE Leap

Information for package perl-File-ShareDir:
-------------------------------------------
Repository : Main Repository
Name : perl-File-ShareDir
Version : 1.104-1.22
Arch : noarch
Vendor : SUSE LLC
Installed Size : 45.1 KiB
Installed : No
Status : not installed
Source package : perl-File-ShareDir-1.104-1.22.src
Upstream URL : http://search.cpan.org/dist/File-ShareDir/
Summary : Locate per-dist and per-module shared files
Description :
The intent of File::ShareDir is to provide a companion to Class::Inspector
and File::HomeDir, modules that take a process that is well-known by
advanced Perl developers but gets a little tricky, and make it more
available to the larger Perl community.
Quite often you want or need your Perl module (CPAN or otherwise) to have
access to a large amount of read-only data that is stored on the
file-system at run-time.
On a linux-like system, this would be in a place such as /usr/share,
however Perl runs on a wide variety of different systems, and so the use of
any one location is unreliable.
Perl provides a little-known method for doing this, but almost nobody is
aware that it exists. As a result, module authors often go through some
very strange ways to make the data available to their code.
The most common of these is to dump the data out to an enormous Perl data
structure and save it into the module itself. The result are enormous
multi-megabyte .pm files that chew up a lot of memory needlessly.
Another method is to put the data "file" after the __DATA__ compiler tag
and limit yourself to access as a filehandle.
The problem to solve is really quite simple.
1. Write the data files to the system at install time.
2. Know where you put them at run-time.
Perl's install system creates an "auto" directory for both every
distribution and for every module file.
These are used by a couple of different auto-loading systems to store code
fragments generated at install time, and various other modules written by
the Perl "ancient masters".
But the same mechanism is available to any dist or module to store any sort
of data.