From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] buildman: Perform tests in /tmp
Date: Fri, 4 Oct 2019 16:07:02 -0400 [thread overview]
Message-ID: <20191004200702.GF15735@bill-the-cat> (raw)
In-Reply-To: <57edce01-e4ad-69ab-21f1-11037513579d@wwwdotorg.org>
On Fri, Oct 04, 2019 at 12:40:02PM -0600, Stephen Warren wrote:
> On 10/4/19 11:26 AM, Tom Rini wrote:
> > On Fri, Oct 04, 2019 at 10:32:42AM -0600, Stephen Warren wrote:
> > > On 10/4/19 10:12 AM, Tom Rini wrote:
> > > > We may not always be able to write to the default output directory but
> > > > we will always have a usable /tmp.
> > >
> > > Is that a valid assumption? Surely $TMPDIR should be used if set in the
> > > environment, falling back to a hard-coded /tmp if that isn't set?
> >
> > $TMPDIR is most portable but as far as Linux goes, there needs to be
> > /tmp, yes?
>
> I don't think there absolutely has to be, no. Calling tempfile.mkdtemp()
> will "just work" and do the right thing in all cases.
OK, that wasn't too bad, waiting for any other feedback before v2'ing,
thanks.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191004/d1cae8be/attachment.sig>
next prev parent reply other threads:[~2019-10-04 20:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 16:12 [U-Boot] [PATCH 1/3] buildman: Perform tests in /tmp Tom Rini
2019-10-04 16:12 ` [U-Boot] [PATCH 2/3] gitlab-ci: Have buildman use /tmp for output Tom Rini
2019-10-04 16:34 ` Stephen Warren
2019-10-04 17:28 ` Tom Rini
2019-10-08 22:38 ` Tom Rini
2019-10-04 16:12 ` [U-Boot] [PATCH 3/3] gitlab-ci: Switch to Ubuntu 18.04 image Tom Rini
2019-10-08 22:38 ` Tom Rini
2019-10-04 16:32 ` [U-Boot] [PATCH 1/3] buildman: Perform tests in /tmp Stephen Warren
2019-10-04 17:26 ` Tom Rini
2019-10-04 18:40 ` Stephen Warren
2019-10-04 20:07 ` Tom Rini [this message]
2019-10-10 17:06 ` Simon Glass
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=20191004200702.GF15735@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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