From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stepnem@smrk.net>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-3.4 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI,SPF_HELO_NONE,
	SPF_PASS,T_SCC_BODY_TEXT_LINE shortcircuit=no autolearn=ham
	autolearn_force=no version=3.4.6
Received: from mail.smrk.net (mail.smrk.net [IPv6:2001:19f0:6c01:2788:5400:4ff:fe27:adaa])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512)
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id 80DF91F4B8
	for <meta@public-inbox.org>; Thu,  1 Feb 2024 10:15:16 +0000 (UTC)
Authentication-Results: dcvr.yhbt.net;
	dkim=pass (2048-bit key; unprotected) header.d=smrk.net header.i=@smrk.net header.a=rsa-sha256 header.s=20221002 header.b=nyj+3b5w;
	dkim-atps=neutral
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=smrk.net; s=20221002;
	t=1706782513;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=HBFOX6zNl+2k6c+Nrehuymx7ONWNICXpv+qcLvpyXG0=;
	b=nyj+3b5wguFv9C5B1ZyqNMWn2+o/h65lWi03fbKFNbU3MzDpISKqxmDm/WdjZsEydaN1bh
	I8xOFXHaSxqvjHBriPmdo17Wcvt5J0QKToVq5gxAXHsYRscHWp2aRMOuP8MjpaOXS+V+Nx
	/xrIJ6PFfX6FLL/+rWHtFLYNKyJeLk8xLE0bGgVYUujH58BPScijVJY062O3Fuc/7Vs8h+
	1s0nYqVdCdbOh4TfNAoc0vP16SXO2+TTtO9YqlznBbl4WbHZG+s3o89Tpqib678BaPJ9PX
	pz6clv1JkYH7L9u2lVB+G90us5UMctSfePfuR4sp8C3PoIySmUDAthhrply+pA==
Received: from localhost (<unknown> [192.168.5.2])
	by smrk (OpenSMTPD) with ESMTPSA id 20ba1c31 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO);
	Thu, 1 Feb 2024 11:15:13 +0100 (CET)
From: =?utf-8?B?xaB0xJtww6FuIE7Em21lYw==?= <stepnem@smrk.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] pop3d: support fcntl locks on OpenBSD i386
In-Reply-To: <20240201001219.1314010-1-e@80x24.org> (Eric Wong's message of
	"Thu, 1 Feb 2024 00:12:19 +0000")
References: <20240201001219.1314010-1-e@80x24.org>
User-Agent: Gnus/5.13 (Gnus v5.13)
Date: Thu, 01 Feb 2024 11:15:12 +0100
Message-ID: <20240201111512+0100.214403-stepnem@smrk.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-Id: <meta.public-inbox.org>

On Thu,  1 Feb 2024 00:12:19 +0000
Eric Wong wrote:

> AFAIK File::FcntlLock isn't packaged for OpenBSD,

https://openports.pl/path/devel/p5-File-FcntlLock
https://ftp.openbsd.org/pub/OpenBSD/snapshots/packages/amd64/p5-File-FcntlL=
ock-0.22.tgz

(apparently only added a few months ago, so it's not in any
release yet; should be available starting with 7.5 (due in
May or thereabouts))

--=20
=C5=A0t=C4=9Bp=C3=A1n