How to Install and Uninstall ghc-atomic-write.x86_64 Package on Fedora 36
Last updated: November 27,2024
1. Install "ghc-atomic-write.x86_64" package
Please follow the guidance below to install ghc-atomic-write.x86_64 on Fedora 36
$
sudo dnf update
Copied
$
sudo dnf install
ghc-atomic-write.x86_64
Copied
2. Uninstall "ghc-atomic-write.x86_64" package
Please follow the instructions below to uninstall ghc-atomic-write.x86_64 on Fedora 36:
$
sudo dnf remove
ghc-atomic-write.x86_64
Copied
$
sudo dnf autoremove
Copied
3. Information about the ghc-atomic-write.x86_64 package on Fedora 36
Last metadata expiration check: 1:16:51 ago on Thu Sep 8 02:05:26 2022.
Available Packages
Name : ghc-atomic-write
Version : 0.2.0.7
Release : 5.fc36
Architecture : x86_64
Size : 24 k
Source : ghc-atomic-write-0.2.0.7-5.fc36.src.rpm
Repository : fedora
Summary : Atomically write to a file
URL : https://hackage.haskell.org/package/atomic-write
License : MIT
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.
Available Packages
Name : ghc-atomic-write
Version : 0.2.0.7
Release : 5.fc36
Architecture : x86_64
Size : 24 k
Source : ghc-atomic-write-0.2.0.7-5.fc36.src.rpm
Repository : fedora
Summary : Atomically write to a file
URL : https://hackage.haskell.org/package/atomic-write
License : MIT
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.