From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross@burtonini.com>, Enrico J?rns <ejo@pengutronix.de>
Cc: Khem Raj <raj.khem@gmail.com>,
Jacob Kroon <jacob.kroon@gmail.com>,
"Robert P. J. Day" <rpjday@crashcourse.ca>,
OE Core mailing list <openembedded-core@lists.openembedded.org>,
jlu@pengutronix.de
Subject: Re: [OE-core] [PATCH] remove unused DEPLOY_DIR_TOOLS variable from bitbake.conf
Date: Tue, 09 Jun 2020 15:21:12 +0100 [thread overview]
Message-ID: <d8a4e2fc32bfec3e84d3e2ca6036e2ff74c755ba.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAAnfSTsshwC-aOTMR=6rx-04QaoVDJh3L6Turr1MsBwH2sbCFA@mail.gmail.com>
On Tue, 2020-06-09 at 14:33 +0100, Ross Burton wrote:
> On Mon, 8 Jun 2020 at 21:15, Enrico J?rns <ejo@pengutronix.de> wrote:
>
> > What is the now suggested way of placing these kind of binaries?
> > Simply in DEPLOY_DIR_IMAGES as the above-mentioned commit does
> > (silently)?
> > Or is there maybe still some motivation to keep DEPLOY_DIR_TOOLS?
>
> FWIW, meta-arm is also using DEPLOY_DIR_TOOLS and to fix builds with
> master is now manually using DEPLOY_DIR/tools because having a
> separate directory does help introduce some structure.
>
> Basically, I'd actually like to see this reverted.
I'm tempted to agree. It was only merged on the basis that it was
unused which isn't true.
Cheers,
Richard
next prev parent reply other threads:[~2020-06-09 14:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 14:31 [PATCH] remove unused DEPLOY_DIR_TOOLS variable from bitbake.conf Robert P. J. Day
2020-05-27 14:36 ` [OE-core] " Jacob Kroon
2020-05-29 2:02 ` Khem Raj
2020-06-08 20:15 ` Enrico J?rns
2020-06-08 20:44 ` Khem Raj
2020-06-09 13:33 ` Ross Burton
2020-06-09 14:21 ` Richard Purdie [this message]
2020-06-09 14:33 ` Robert P. J. Day
2020-05-27 15:02 ` ✗ patchtest: failure for " Patchwork
[not found] <1612E913BFE72856.28111@lists.openembedded.org>
2020-05-27 14:38 ` [OE-core] [PATCH] " Robert P. J. Day
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=d8a4e2fc32bfec3e84d3e2ca6036e2ff74c755ba.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=ejo@pengutronix.de \
--cc=jacob.kroon@gmail.com \
--cc=jlu@pengutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=ross@burtonini.com \
--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.