How to Install and Uninstall php-doctrine-deprecations.noarch Package on Fedora 39
Last updated: November 26,2024
1. Install "php-doctrine-deprecations.noarch" package
This guide let you learn how to install php-doctrine-deprecations.noarch on Fedora 39
$
sudo dnf update
Copied
$
sudo dnf install
php-doctrine-deprecations.noarch
Copied
2. Uninstall "php-doctrine-deprecations.noarch" package
This is a short guide on how to uninstall php-doctrine-deprecations.noarch on Fedora 39:
$
sudo dnf remove
php-doctrine-deprecations.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the php-doctrine-deprecations.noarch package on Fedora 39
Last metadata expiration check: 1:05:30 ago on Thu Mar 7 17:44:52 2024.
Available Packages
Name : php-doctrine-deprecations
Version : 1.1.3
Release : 1.fc39.remi
Architecture : noarch
Size : 14 k
Source : php-doctrine-deprecations-1.1.3-1.fc39.remi.src.rpm
Repository : remi
Summary : A small layer on top of triggeFr_error or PSR-3 logging
URL : https://github.com/doctrine/deprecations
License : MIT
Description : A small (side-effect free by default) layer on top of
: trigger_error(E_USER_DEPRECATED) or PSR-3 logging.
:
: * no side-effects by default, making it a perfect fit for libraries
: that don't know how the error handler works they operate under
: * options to avoid having to rely on error handlers global state by
: using PSR-3 logging
: * deduplicate deprecation messages to avoid excessive triggering and
: reduce overhead
:
: We recommend to collect Deprecations using a PSR logger instead of
: relying on the global error handler.
:
: Autoloader: /usr/share/php/Doctrine/Deprecations/autoload.php
Available Packages
Name : php-doctrine-deprecations
Version : 1.1.3
Release : 1.fc39.remi
Architecture : noarch
Size : 14 k
Source : php-doctrine-deprecations-1.1.3-1.fc39.remi.src.rpm
Repository : remi
Summary : A small layer on top of triggeFr_error or PSR-3 logging
URL : https://github.com/doctrine/deprecations
License : MIT
Description : A small (side-effect free by default) layer on top of
: trigger_error(E_USER_DEPRECATED) or PSR-3 logging.
:
: * no side-effects by default, making it a perfect fit for libraries
: that don't know how the error handler works they operate under
: * options to avoid having to rely on error handlers global state by
: using PSR-3 logging
: * deduplicate deprecation messages to avoid excessive triggering and
: reduce overhead
:
: We recommend to collect Deprecations using a PSR logger instead of
: relying on the global error handler.
:
: Autoloader: /usr/share/php/Doctrine/Deprecations/autoload.php