How to Install and Uninstall ghc-retry Package on openSuSE Tumbleweed
Last updated: December 27,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "ghc-retry" package
Please follow the steps below to install ghc-retry on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
ghc-retry
Copied
2. Uninstall "ghc-retry" package
Please follow the guidance below to uninstall ghc-retry on openSuSE Tumbleweed:
$
sudo zypper remove
ghc-retry
Copied
3. Information about the ghc-retry package on openSuSE Tumbleweed
Information for package ghc-retry:
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : ghc-retry
Version : 0.9.0.0-1.7
Arch : x86_64
Vendor : openSUSE
Installed Size : 136,7 KiB
Installed : No
Status : not installed
Source package : ghc-retry-0.9.0.0-1.7.src
Summary : Retry combinators for monadic actions that may fail
Description :
This package exposes combinators that can wrap arbitrary monadic actions.
They run the action and potentially retry running it with some configurable
delay for a configurable number of times. The purpose is to make it easier to
work with IO and especially network IO actions that often experience temporary
failure and warrant retrying of the original action. For example, a database
query may time out for a while, in which case we should hang back for a bit and
retry the query instead of simply raising an exception.
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : ghc-retry
Version : 0.9.0.0-1.7
Arch : x86_64
Vendor : openSUSE
Installed Size : 136,7 KiB
Installed : No
Status : not installed
Source package : ghc-retry-0.9.0.0-1.7.src
Summary : Retry combinators for monadic actions that may fail
Description :
This package exposes combinators that can wrap arbitrary monadic actions.
They run the action and potentially retry running it with some configurable
delay for a configurable number of times. The purpose is to make it easier to
work with IO and especially network IO actions that often experience temporary
failure and warrant retrying of the original action. For example, a database
query may time out for a while, in which case we should hang back for a bit and
retry the query instead of simply raising an exception.