From: Marek Szuba <marecki@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/5] gnome2-utils.eclass: phase out emktemp
Date: Sun, 26 Dec 2021 09:44:28 +0000 [thread overview]
Message-ID: <B7D6BA77-536F-406B-9A7A-B3B7F0F61624@gentoo.org> (raw)
In-Reply-To: <136a9c8c1a600ca22f4facdb8de8feb3ba0bb818.camel@gentoo.org>
On 13 December 2021 17:24:18 UTC, Mart Raudsepp <leio@gentoo.org> wrote:
>Actually I kind of preferred a static name over straight mktemp,
>because emktemp supported other cases than a pure mktemp usage does.
>But I don't know if it could ever clash things in some weird
>situations.
That last part is the message I tried to convey in my e-mail, sorry if I wasn't clear enough.
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.g. to use static names with EAPI-8+ but stick with mktemp for older EAPIs just to be safe.
--
Marecki
next prev parent reply other threads:[~2021-12-26 9:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 13:23 [gentoo-dev] [PATCH 0/5] EAPI-8 support in gnome2{,-utils}.eclass Marek Szuba
2021-12-09 13:23 ` [gentoo-dev] [PATCH 1/5] gnome2-utils.eclass: phase out emktemp Marek Szuba
2021-12-09 15:04 ` Michał Górny
2021-12-13 10:19 ` Marek Szuba
2021-12-13 17:24 ` Mart Raudsepp
2021-12-26 9:44 ` Marek Szuba [this message]
2021-12-26 9:50 ` Michał Górny
2021-12-26 10:17 ` Mart Raudsepp
2021-12-09 13:23 ` [gentoo-dev] [PATCH 2/5] gnome2-utils.eclass: support EAPI 8 Marek Szuba
2021-12-09 13:23 ` [gentoo-dev] [PATCH 3/5] gnome2.eclass: do not call xdg_src_prepare Marek Szuba
2021-12-09 13:23 ` [gentoo-dev] [PATCH 4/5] gnome2.eclass: standardise the EAPI guard Marek Szuba
2021-12-09 13:23 ` [gentoo-dev] [PATCH 5/5] gnome2.eclass: support EAPI 8 Marek Szuba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B7D6BA77-536F-406B-9A7A-B3B7F0F61624@gentoo.org \
--to=marecki@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox