From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/5] gnome2-utils.eclass: phase out emktemp
Date: Mon, 13 Dec 2021 19:24:18 +0200 [thread overview]
Message-ID: <136a9c8c1a600ca22f4facdb8de8feb3ba0bb818.camel@gentoo.org> (raw)
In-Reply-To: <c064c402-41f2-1aa2-a666-a6bfce00c4a0@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1448 bytes --]
Ühel kenal päeval, E, 13.12.2021 kell 10:19, kirjutas Marek Szuba:
> On 2021-12-09 15:04, Michał Górny wrote:
>
> > Why do you need to use random name in the first place? We have
> > full
> > control over T, so why not just hardcode a good name?
>
> Having discussed the matter with eclass maintainers on IRC, they are
> not
> entirely sure whether using a static name in this context is entirely
> safe. There were also concerns about making this change too
> aggressive
> given it affects all supported EAPIs. Therefore, we have decided to
> play
> it safe and stick as closely to old behaviour as possible, at least
> for now.
>
> Anyway, merged a moment ago.
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. I think they won't, but I don't know if PMS guarantees that
or just happens how portage works right now (e.g. the postrm currently
happening in a separate ._unmerge directory path for $T; multilib
postinst happening sequentially, etc).
Thinking it through again a bit, straight mktemp can't be worse than a
static name anyways (provided mktemp exists, which emktemp handled..),
so we're good there, but provided you or someone thinks through the
corner-cases, I'm in favor of a static name if it doesn't have any
trouble.
Mart
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2021-12-13 17:24 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 [this message]
2021-12-26 9:44 ` Marek Szuba
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=136a9c8c1a600ca22f4facdb8de8feb3ba0bb818.camel@gentoo.org \
--to=leio@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