From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] classes: Replace "if test" file tests with POSIX file tests
Date: Tue, 28 Mar 2017 11:47:32 +0100 [thread overview]
Message-ID: <1490698052.13980.274.camel@linuxfoundation.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1703280554060.2771@uk63952.mitel.com>
On Tue, 2017-03-28 at 05:56 -0400, Robert P. J. Day wrote:
> On Mon, 27 Mar 2017, Richard Purdie wrote:
>
> >
> > On Sat, 2017-03-25 at 14:03 -0400, Robert P. J. Day wrote:
> > >
> > > In entire meta/classes/ directory, replace shell tests of the
> > > form
> > > "if test -? ..." with POSIX tests of the form "if [ -? ...
> > >
> > > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
> > >
> > > ---
> > >
> > > as i cannot abide those silly "if test" constructs, i zipped
> > > through
> > > and changed them to POSIX form. is there any objection to this
> > > kind
> > > of
> > > cleanup? next up ... all those "x${VAR} = x" tests ...
> > I've merged most of this. There were pieces of the diff that simply
> > didn't apply so I skipped them.
> >
> > The reason I've taken what applied is that this is very expensive
> > for us to test right now and I made the most of the testing time I
> > had on the weekend. The issue is changes to the core classes
> > rebuild
> > everything so we can't reuse sstate and the tests are much slower.
> >
> > We're running late with M3 rc2 but just about to build it and I
> > thought it was worth getting some of this in rather none at all.
> > Please do figure out the remaining pieces and send them and we may
> > or may not tweak the remaining bits in M4.
> my next cleanup was going to be (as mentioned above) replace all
> those silly "x${VAR} = x" string tests with either of:
>
> [ -z "${VAR}" ]
> [ -n "${VAR}" ]
>
> is there time to get that in before the next freeze? if so, i can do
> it quickly for testing; if not, i guess it can just wait.
I think that needs to wait for 2.4 but I agree its worth cleaning that
up.
Cheers,
Richard
prev parent reply other threads:[~2017-03-28 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 18:03 [PATCH] classes: Replace "if test" file tests with POSIX file tests Robert P. J. Day
2017-03-25 18:32 ` ✗ patchtest: failure for " Patchwork
2017-03-27 13:31 ` [PATCH] " Richard Purdie
2017-03-28 9:56 ` Robert P. J. Day
2017-03-28 10:46 ` Peter Kjellerstedt
2017-03-28 10:54 ` Robert P. J. Day
2017-03-28 13:42 ` Patrick Ohly
2017-03-28 10:47 ` Richard Purdie [this message]
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=1490698052.13980.274.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.