| Message ID | 20220909151221.434124-1-otavio@ossystems.com.br |
|---|---|
| State | Accepted, archived |
| Commit | c53b2539176199607eb12c706658a269c81d3232 |
| Headers | show |
| Series | [v2] rust-hello-world: move to recipes-extended | expand |
On Fri, 2022-09-09 at 12:12 -0300, Otavio Salvador wrote: > There is no need to have a single recipe in recipes-example; moving it > to recipes-extended allow it being use inside QA tests. I'm a bit puzzled why it doesn't work from it's current location? Cheers, Richard
Em sex., 9 de set. de 2022 às 12:16, Richard Purdie < richard.purdie@linuxfoundation.org> escreveu: > On Fri, 2022-09-09 at 12:12 -0300, Otavio Salvador wrote: > > There is no need to have a single recipe in recipes-example; moving it > > to recipes-extended allow it being use inside QA tests. > > I'm a bit puzzled why it doesn't work from it's current location? > It does but recipes-example only has this recipe.
On Fri, 2022-09-09 at 13:14 -0300, Otavio Salvador wrote: > > > Em sex., 9 de set. de 2022 às 12:16, Richard Purdie > <richard.purdie@linuxfoundation.org> escreveu: > > On Fri, 2022-09-09 at 12:12 -0300, Otavio Salvador wrote: > > > There is no need to have a single recipe in recipes-example; > > > moving it > > > to recipes-extended allow it being use inside QA tests. > > > > I'm a bit puzzled why it doesn't work from it's current location? > > > > > It does but recipes-example only has this recipe. That makes the commit message a bit misleading then as it doesn't fix any QA test. Cheers, Richard
Em sex., 9 de set. de 2022 às 13:49, Richard Purdie < richard.purdie@linuxfoundation.org> escreveu: > On Fri, 2022-09-09 at 13:14 -0300, Otavio Salvador wrote: > > Em sex., 9 de set. de 2022 às 12:16, Richard Purdie > > <richard.purdie@linuxfoundation.org> escreveu: > > > On Fri, 2022-09-09 at 12:12 -0300, Otavio Salvador wrote: > > > > There is no need to have a single recipe in recipes-example; > > > > moving it > > > > to recipes-extended allow it being use inside QA tests. > > > > > > I'm a bit puzzled why it doesn't work from it's current location? > > > > > > > > > It does but recipes-example only has this recipe. > > > That makes the commit message a bit misleading then as it doesn't fix > any QA test. > I'll send a v3.
diff --git a/meta/recipes-example/rust-hello-world/rust-hello-world/0001-enable-LTO.patch b/meta/recipes-extended/rust-example/rust-hello-world/0001-enable-LTO.patch similarity index 100% rename from meta/recipes-example/rust-hello-world/rust-hello-world/0001-enable-LTO.patch rename to meta/recipes-extended/rust-example/rust-hello-world/0001-enable-LTO.patch diff --git a/meta/recipes-example/rust-hello-world/rust-hello-world_git.bb b/meta/recipes-extended/rust-example/rust-hello-world_git.bb similarity index 100% rename from meta/recipes-example/rust-hello-world/rust-hello-world_git.bb rename to meta/recipes-extended/rust-example/rust-hello-world_git.bb
There is no need to have a single recipe in recipes-example; moving it to recipes-extended allow it being use inside QA tests. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> --- Changes in v2: - move from recipes-example to recipes-extended .../rust-example}/rust-hello-world/0001-enable-LTO.patch | 0 .../rust-example}/rust-hello-world_git.bb | 0 2 files changed, 0 insertions(+), 0 deletions(-) rename meta/{recipes-example/rust-hello-world => recipes-extended/rust-example}/rust-hello-world/0001-enable-LTO.patch (100%) rename meta/{recipes-example/rust-hello-world => recipes-extended/rust-example}/rust-hello-world_git.bb (100%)