head	1.2;
access;
symbols
	pkgsrc-2026Q1:1.2.0.10
	pkgsrc-2026Q1-base:1.2
	pkgsrc-2025Q4:1.2.0.8
	pkgsrc-2025Q4-base:1.2
	pkgsrc-2025Q3:1.2.0.6
	pkgsrc-2025Q3-base:1.2
	pkgsrc-2025Q2:1.2.0.4
	pkgsrc-2025Q2-base:1.2
	pkgsrc-2025Q1:1.2.0.2
	pkgsrc-2025Q1-base:1.2
	pkgsrc-2024Q4:1.1.0.24
	pkgsrc-2024Q4-base:1.1
	pkgsrc-2024Q3:1.1.0.22
	pkgsrc-2024Q3-base:1.1
	pkgsrc-2024Q2:1.1.0.20
	pkgsrc-2024Q2-base:1.1
	pkgsrc-2024Q1:1.1.0.18
	pkgsrc-2024Q1-base:1.1
	pkgsrc-2023Q4:1.1.0.16
	pkgsrc-2023Q4-base:1.1
	pkgsrc-2023Q3:1.1.0.14
	pkgsrc-2023Q3-base:1.1
	pkgsrc-2023Q2:1.1.0.12
	pkgsrc-2023Q2-base:1.1
	pkgsrc-2023Q1:1.1.0.10
	pkgsrc-2023Q1-base:1.1
	pkgsrc-2022Q4:1.1.0.8
	pkgsrc-2022Q4-base:1.1
	pkgsrc-2022Q3:1.1.0.6
	pkgsrc-2022Q3-base:1.1
	pkgsrc-2022Q2:1.1.0.4
	pkgsrc-2022Q2-base:1.1
	pkgsrc-2022Q1:1.1.0.2
	pkgsrc-2022Q1-base:1.1;
locks; strict;
comment	@# @;


1.2
date	2025.01.31.15.56.11;	author pho;	state Exp;
branches;
next	1.1;
commitid	DlkZ20NyCMhSAEHF;

1.1
date	2022.02.23.16.52.15;	author pho;	state Exp;
branches;
next	;
commitid	0nDaw3jWJTSuoLtD;


desc
@@


1.2
log
@devel/hs-atomic-write: update to atomic-write-0.2.1.0

No release notes have been provided by the upstream.
@
text
@$NetBSD: distinfo,v 1.1 2022/02/23 16:52:15 pho Exp $

BLAKE2s (atomic-write-0.2.1.0.tar.gz) = 609a3755fccf79255938f53653a26b4641d6d2ecb8e48e7748a76f98fa202648
SHA512 (atomic-write-0.2.1.0.tar.gz) = 5ff555fd3d72de2b613ecd0445e5ec5f45c1ca722947c67709e6c622a52522d05d6b3f54d02b5f3f4babf1864aa7735a6bee7634453c71942cd76f107a8e1a89
Size (atomic-write-0.2.1.0.tar.gz) = 7266 bytes
@


1.1
log
@devel/hs-atomic-write: import hs-atomic-write-0.2.0.7

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 mving 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.
@
text
@d1 1
a1 1
$NetBSD$
d3 3
a5 3
BLAKE2s (atomic-write-0.2.0.7.tar.gz) = 66d3c8b459d6fbe075c03e69cbd27e67c6f6067a412aaccecf9268342e7823dc
SHA512 (atomic-write-0.2.0.7.tar.gz) = 3405437b801fbdd542c5c8a403f603ccb65ceaa63beca15062c429eaea412d7006342eb237982c9fe6751ffd160f810197b30fec3e49528e51bae1fc7f47af2e
Size (atomic-write-0.2.0.7.tar.gz) = 7199 bytes
@