How to Install and Uninstall ghc-atomic-write Package on openSUSE Leap
Last updated: November 07,2024
1. Install "ghc-atomic-write" package
Learn how to install ghc-atomic-write on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
ghc-atomic-write
Copied
2. Uninstall "ghc-atomic-write" package
Please follow the step by step instructions below to uninstall ghc-atomic-write on openSUSE Leap:
$
sudo zypper remove
ghc-atomic-write
Copied
3. Information about the ghc-atomic-write package on openSUSE Leap
Information for package ghc-atomic-write:
-----------------------------------------
Repository : Main Repository
Name : ghc-atomic-write
Version : 0.2.0.7-bp155.2.17
Arch : x86_64
Vendor : openSUSE
Installed Size : 76.3 KiB
Installed : No
Status : not installed
Source package : ghc-atomic-write-0.2.0.7-bp155.2.17.src
Upstream URL : https://hackage.haskell.org/package/atomic-write
Summary : Atomically write to a file
Description :
Atomically write to a file on POSIX-compliant systems while preserving
permissions.
On most Unix systems, `mv` is an atomic operation. This makes it simple to
write to a file atomically just by using the mv operation. However, this will
destroy the permissions on the original file. This library does the following
to preserve permissions while atomically writing to a file:
* If an original file exists, take those permissions and apply them to the temp
file before `mv`ing the file into place.
* If the original file does not exist, create a following with default
permissions (based on the currently-active umask).
This way, when the file is `mv`'ed into place, the permissions will be the ones
held by the original file.
This library is based on similar implementations found in common libraries in
Ruby and Python:
*
similar method called atomic_write>
*
Chef includes atomic update functionality>
*
atomically updating a file>
To use `atomic-write`, import the module corresponding to the type you wish to
write atomically, e.g., to write a (strict) ByteString atomically:
> import System.AtomicWrite.Writer.ByteString
Then you can use the atomicWriteFile function that accepts a `FilePath` and a
`ByteString`, e.g.:
> atomicWriteFile myFilePath myByteString.
-----------------------------------------
Repository : Main Repository
Name : ghc-atomic-write
Version : 0.2.0.7-bp155.2.17
Arch : x86_64
Vendor : openSUSE
Installed Size : 76.3 KiB
Installed : No
Status : not installed
Source package : ghc-atomic-write-0.2.0.7-bp155.2.17.src
Upstream URL : https://hackage.haskell.org/package/atomic-write
Summary : Atomically write to a file
Description :
Atomically write to a file on POSIX-compliant systems while preserving
permissions.
On most Unix systems, `mv` is an atomic operation. This makes it simple to
write to a file atomically just by using the mv operation. However, this will
destroy the permissions on the original file. This library does the following
to preserve permissions while atomically writing to a file:
* If an original file exists, take those permissions and apply them to the temp
file before `mv`ing the file into place.
* If the original file does not exist, create a following with default
permissions (based on the currently-active umask).
This way, when the file is `mv`'ed into place, the permissions will be the ones
held by the original file.
This library is based on similar implementations found in common libraries in
Ruby and Python:
*
*
*
To use `atomic-write`, import the module corresponding to the type you wish to
write atomically, e.g., to write a (strict) ByteString atomically:
> import System.AtomicWrite.Writer.ByteString
Then you can use the atomicWriteFile function that accepts a `FilePath` and a
`ByteString`, e.g.:
> atomicWriteFile myFilePath myByteString.