From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id D1AF8158086 for ; Sun, 26 Dec 2021 09:44:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A72EE2BC023; Sun, 26 Dec 2021 09:44:38 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 8384D2BC018 for ; Sun, 26 Dec 2021 09:44:36 +0000 (UTC) Date: Sun, 26 Dec 2021 09:44:28 +0000 From: Marek Szuba To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [PATCH 1/5] gnome2-utils.eclass: phase out emktemp User-Agent: K-9 Mail for Android In-Reply-To: <136a9c8c1a600ca22f4facdb8de8feb3ba0bb818.camel@gentoo.org> References: <20211209132325.297913-1-marecki@gentoo.org> <20211209132325.297913-2-marecki@gentoo.org> <1f731fd5d6309bf1ebeb8e08b73ca903a1bc47dc.camel@gentoo.org> <136a9c8c1a600ca22f4facdb8de8feb3ba0bb818.camel@gentoo.org> Message-ID: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: fe53695c-2d88-41a3-8d06-f42a303c2886 X-Archives-Hash: 9b89297260c63d245ea2dd9ea1cfc66e On 13 December 2021 17:24:18 UTC, Mart Raudsepp wrote: >Actually I kind of preferred a static name over straight mktemp, >because emktemp supported other cases than a pure mktemp usage does=2E >But I don't know if it could ever clash things in some weird >situations=2E That last part is the message I tried to convey in my e-mail, sorry if I w= asn't clear enough=2E Anyway, could anyone with more Postage/PMS experience weigh in on this? If= it is indeed safe then the eclass could be modified further, e=2Eg=2E to u= se static names with EAPI-8+ but stick with mktemp for older EAPIs just to = be safe=2E --=20 Marecki