All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Mikko.Rapeli@bmw.de
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/7] ncurses: Don't put terminfo into the sysroot
Date: Thu, 28 Jan 2021 10:52:07 +0000	[thread overview]
Message-ID: <38a7b6cebff89a5de774dd5bda527a7e5f725a85.camel@linuxfoundation.org> (raw)
In-Reply-To: <YBKTg29d2wdbT2Lv@korppu>

On Thu, 2021-01-28 at 10:35 +0000, Mikko.Rapeli@bmw.de wrote:
> On Thu, Jan 28, 2021 at 09:02:39AM +0000, Richard Purdie wrote:
> > On Thu, 2021-01-28 at 08:45 +0000, Mikko.Rapeli@bmw.de wrote:
> > > Interesting series! Do you already have some numbers how this affects
> > > bitbake builds?
> > 
> > Not yet. I should really have split the series into two, the files
> > reduction and the native PACKAGES pieces as the latter is proving quite
> > unstable on the autobuilder and holding the other up. Once it does
> > build cleanly and merges, we will get build time measurements which I'm
> > curious about too.
> 
> Yes, split would have been nice. I'm seeing issues after porting over
> to dunfell :)

They don't depend on each other so you can just pick the sysroot
cleaning ones. master-next has some updated patches which are doing
better too.

Cheers,

Richard


  reply	other threads:[~2021-01-28 10:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 17:27 [PATCH 1/7] ncurses: Don't put terminfo into the sysroot Richard Purdie
2021-01-27 17:27 ` [PATCH 2/7] python3: Avoid installing test data into recipe-sysroot Richard Purdie
2021-01-27 17:27 ` [PATCH 3/7] staging: Clean up files installed into the sysroot Richard Purdie
2021-01-27 17:27 ` [PATCH 4/7] gobject-introspection: Fix variable override order Richard Purdie
2021-01-27 17:27 ` [PATCH 5/7] bitbake.conf/python: Drop setting RDEPENDS/RPROVIDES default Richard Purdie
2021-01-27 17:27 ` [PATCH 6/7] native: Stop clearing PACKAGES Richard Purdie
2021-01-30 16:15   ` [OE-core] " Martin Jansa
2021-01-31  9:07     ` Richard Purdie
2021-01-31  9:55       ` Martin Jansa
2021-01-31 10:34         ` Richard Purdie
2021-01-31 13:10           ` Martin Jansa
2021-02-01 14:26             ` Anibal Limon
2021-02-01 20:21             ` Richard Purdie
2021-02-01 20:44               ` Martin Jansa
2021-02-04 19:43   ` Peter Kjellerstedt
2021-02-04 20:34     ` Richard Purdie
2021-01-27 17:27 ` [PATCH 7/7] meta: Clean up various class-native* RDEPENDS overrides Richard Purdie
2021-01-28  8:45 ` [OE-core] [PATCH 1/7] ncurses: Don't put terminfo into the sysroot Mikko Rapeli
2021-01-28  9:02   ` Richard Purdie
2021-01-28 10:35     ` Mikko Rapeli
2021-01-28 10:52       ` Richard Purdie [this message]
2021-01-28 16:38   ` Richard Purdie
2021-01-29  8:28     ` Mikko Rapeli

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=38a7b6cebff89a5de774dd5bda527a7e5f725a85.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Mikko.Rapeli@bmw.de \
    --cc=openembedded-core@lists.openembedded.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 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.