How to Install and Uninstall scala-stm Package on openSuSE Tumbleweed
Last updated: March 03,2025
1. Install "scala-stm" package
In this section, we are going to explain the necessary steps to install scala-stm on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
scala-stm
Copied
2. Uninstall "scala-stm" package
Here is a brief guide to show you how to uninstall scala-stm on openSuSE Tumbleweed:
$
sudo zypper remove
scala-stm
Copied
3. Information about the scala-stm package on openSuSE Tumbleweed
Information for package scala-stm:
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : scala-stm
Version : 0.11.1-1.3
Arch : noarch
Vendor : openSUSE
Installed Size : 599.2 KiB
Installed : No
Status : not installed
Source package : scala-stm-0.11.1-1.3.src
Upstream URL : https://github.com/scala-stm/scala-stm
Summary : Software Transactional Memory for Scala
Description :
ScalaSTM is a lightweight software transactional memory
for Scala, inspired by the STMs in Haskell and Clojure.
ScalaSTM provides a mutable cell called a Ref. If you
build a shared data structure using immutable objects and
Ref-s, then you can access it from multiple threads or
actors. No synchronized, no deadlocks or race conditions,
and good scalability. Included are concurrent sets and
maps, and we also have an easier and safer replacement
for wait and notifyAll.
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : scala-stm
Version : 0.11.1-1.3
Arch : noarch
Vendor : openSUSE
Installed Size : 599.2 KiB
Installed : No
Status : not installed
Source package : scala-stm-0.11.1-1.3.src
Upstream URL : https://github.com/scala-stm/scala-stm
Summary : Software Transactional Memory for Scala
Description :
ScalaSTM is a lightweight software transactional memory
for Scala, inspired by the STMs in Haskell and Clojure.
ScalaSTM provides a mutable cell called a Ref. If you
build a shared data structure using immutable objects and
Ref-s, then you can access it from multiple threads or
actors. No synchronized, no deadlocks or race conditions,
and good scalability. Included are concurrent sets and
maps, and we also have an easier and safer replacement
for wait and notifyAll.