Packages / Fedora 44 / Source / ghc-atomic-write

Source Package: ghc-atomic-write (0.2.1.1-5.fc44)

Atomically write to a file

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: * <http://apidock.com/rails/File/atomic_write/class Ruby on Rails includes a similar method called atomic_write> * <https://github.com/chef/chef/blob/c4631816132fcfefaba3d123a1d0dfe8bc2866bb/lib/chef/file_content_management/deploy/mv_unix.rb#L23:L71 Chef includes atomic update functionality> * <https://github.com/sashka/atomicfile There is a python library for 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.

Package information

Homepage
[https://hackage.haskell.org/package/atomic-write]
License
MIT
Downstream-Paketbetreuer
petersenObserved Nov 20, 2026 [source]

The following binary packages are built from this source package:

Bekannte Sicherheitslücken

Keine passenden Meldungen in den erfassten Quellen.

Zuletzt synchronisiert:

[CVE-Katalog]

Quellen

  • Authoritative source; repository metadata signature verified

    Signaturnachweis

    44-everything-aarch64:ad124f8125666e9059d7a8180427bdaea80f6286f71140457e5c7edd95883eee

    Repository-signature verification record
    Signed-object SHA-256
    236514c32119ab3c85b81fbb9e5e9d92b07aeba0d19d64c9b4fc9117a1863769
    Keyring revision
    RPM-GPG-KEY-fedora-44-primary
    SHA-256 93642aec521a1e5e96dd715f7ae0ec0850ebc9de09a94ce03cae5263f26cc18a
    Tool and policy
    1
    openfactory-software-catalog-signature-v1
    Verification time
    Sep 1, 2026
    Repository metadata hash linkage
    Result
    Recorded as verified; digest details unavailable
  • Authoritative source; repository metadata signature verified

    Signaturnachweis

    44-everything-x86_64:da3845427d188097f6fd71b417a039bdfb8efefc4f38ca44b5cbb94f95a18991

    Repository-signature verification record
    Signed-object SHA-256
    1300b99ac5d04b5561ad901320c8bd59ed1553f4971c3ce2ca48c40242c66676
    Keyring revision
    RPM-GPG-KEY-fedora-44-primary
    SHA-256 93642aec521a1e5e96dd715f7ae0ec0850ebc9de09a94ce03cae5263f26cc18a
    Tool and policy
    1
    openfactory-software-catalog-signature-v1
    Verification time
    Sep 1, 2026
    Repository metadata hash linkage
    Result
    Recorded as verified; digest details unavailable
  • Curated source

    Source observation

    58c9d374bd00b7d29599f0194ec3b0df45a3cdc0fb8d7352b2a2bf869a32237e

    No repository signature was supplied for this metadata.