How to Install and Uninstall php-laminas-memory.noarch Package on Fedora 35
Last updated: November 01,2024
1. Install "php-laminas-memory.noarch" package
In this section, we are going to explain the necessary steps to install php-laminas-memory.noarch on Fedora 35
$
sudo dnf update
Copied
$
sudo dnf install
php-laminas-memory.noarch
Copied
2. Uninstall "php-laminas-memory.noarch" package
Here is a brief guide to show you how to uninstall php-laminas-memory.noarch on Fedora 35:
$
sudo dnf remove
php-laminas-memory.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the php-laminas-memory.noarch package on Fedora 35
Last metadata expiration check: 0:44:47 ago on Wed Sep 7 02:25:42 2022.
Available Packages
Name : php-laminas-memory
Version : 2.9.0
Release : 1.fc35.remi
Architecture : noarch
Size : 20 k
Source : php-laminas-memory-2.9.0-1.fc35.remi.src.rpm
Repository : remi
Summary : Laminas Framework Memory component
URL : https://github.com/laminas/laminas-memory
License : BSD
Description : The Laminas\Memory component is intended to manage data in an environment with
: limited memory.
:
: Memory objects (memory containers) are generated by memory manager by request
: and transparently swapped/loaded when it’s necessary.
:
: For example, if creating or loading a managed object would cause the total
: memory usage to exceed the limit you specify, some managed objects are copied
: to cache storage outside of memory. In this way, the total memory used by
: managed objects does not exceed the limit you need to enforce.
:
: Documentation: https://docs.laminas.dev/laminas-memory/
Available Packages
Name : php-laminas-memory
Version : 2.9.0
Release : 1.fc35.remi
Architecture : noarch
Size : 20 k
Source : php-laminas-memory-2.9.0-1.fc35.remi.src.rpm
Repository : remi
Summary : Laminas Framework Memory component
URL : https://github.com/laminas/laminas-memory
License : BSD
Description : The Laminas\Memory component is intended to manage data in an environment with
: limited memory.
:
: Memory objects (memory containers) are generated by memory manager by request
: and transparently swapped/loaded when it’s necessary.
:
: For example, if creating or loading a managed object would cause the total
: memory usage to exceed the limit you specify, some managed objects are copied
: to cache storage outside of memory. In this way, the total memory used by
: managed objects does not exceed the limit you need to enforce.
:
: Documentation: https://docs.laminas.dev/laminas-memory/