How to Install and Uninstall perl-IPC-SharedCache.noarch Package on Fedora 35
Last updated: November 28,2024
1. Install "perl-IPC-SharedCache.noarch" package
Please follow the guidance below to install perl-IPC-SharedCache.noarch on Fedora 35
$
sudo dnf update
Copied
$
sudo dnf install
perl-IPC-SharedCache.noarch
Copied
2. Uninstall "perl-IPC-SharedCache.noarch" package
Please follow the steps below to uninstall perl-IPC-SharedCache.noarch on Fedora 35:
$
sudo dnf remove
perl-IPC-SharedCache.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the perl-IPC-SharedCache.noarch package on Fedora 35
Last metadata expiration check: 1:49:53 ago on Wed Sep 7 08:25:01 2022.
Available Packages
Name : perl-IPC-SharedCache
Version : 1.3
Release : 46.fc35
Architecture : noarch
Size : 34 k
Source : perl-IPC-SharedCache-1.3-46.fc35.src.rpm
Repository : fedora
Summary : Perl module to manage a cache in SysV IPC shared memory
URL : https://metacpan.org/release/IPC-SharedCache
License : GPLv2+
Description : This module provides a shared memory cache accessed as a tied hash.
: Shared memory is an area of memory that is available to all processes.
: It is accessed by choosing a key, the ipc_key argument to tie. Every
: process that accesses shared memory with the same key gets access to
: the same region of memory. In some ways it resembles a file system,
: but it is not hierarchical and it is resident in memory. This makes
: it harder to use than a filesystem but much faster. The data in
: shared memory persists until the machine is rebooted or it is
: explicitly deleted.
Available Packages
Name : perl-IPC-SharedCache
Version : 1.3
Release : 46.fc35
Architecture : noarch
Size : 34 k
Source : perl-IPC-SharedCache-1.3-46.fc35.src.rpm
Repository : fedora
Summary : Perl module to manage a cache in SysV IPC shared memory
URL : https://metacpan.org/release/IPC-SharedCache
License : GPLv2+
Description : This module provides a shared memory cache accessed as a tied hash.
: Shared memory is an area of memory that is available to all processes.
: It is accessed by choosing a key, the ipc_key argument to tie. Every
: process that accesses shared memory with the same key gets access to
: the same region of memory. In some ways it resembles a file system,
: but it is not hierarchical and it is resident in memory. This makes
: it harder to use than a filesystem but much faster. The data in
: shared memory persists until the machine is rebooted or it is
: explicitly deleted.