From: "Anton Kachalov" <rnouse@google.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [poky][PATCH] bitbake: remove /usr from pseudo ignore paths
Date: Fri, 8 Jan 2021 01:56:44 +0100 [thread overview]
Message-ID: <CADVsX89HCqKYNOyDMK1czkfaOw_TdrwVLK=bi_RanOKgDd=ZuQ@mail.gmail.com> (raw)
In-Reply-To: <63d70805b829d08faf3e73865ed7f9c2ad9a1366.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
Hello, Richard.
Yes, for various reasons we can not move out from /usr/local.
Before the change it works smoothly and we didn't notice about any kind of
performance issues.
May be we can explicitly add various standard subdirs under /usr excluding
/usr/local?
On Thu, Jan 7, 2021, 23:16 Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:
> On Thu, 2021-01-07 at 22:58 +0100, Anton Kachalov via
> lists.openembedded.org wrote:
> > Allow the Yocto's building tree to be placed under /usr.
> >
> > Relevant issue: https://github.com/openbmc/openbmc/issues/3724
> >
> > Signed-off-by: Anton D. Kachalov <rnouse@google.com>
> > ---
> > meta/conf/bitbake.conf | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Do you really need to build under /usr? We probably should make this
> more of a hard error if someone attempts it. I commented on the issue,
> could you just remove this from PSEUDO_IGNORE_PATHS locally if you
> really have to use /usr?
>
> Cheers,
>
> Richard
>
>
[-- Attachment #2: Type: text/html, Size: 1847 bytes --]
next prev parent reply other threads:[~2021-01-08 0:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210107215121.3901938-1-gmouse@google.com>
[not found] ` <CADVsX8-dMLvuccRjzU73=-reDjEBRq5PZZ+S6ZeugSvTy-iqog@mail.gmail.com>
2021-01-07 21:58 ` [poky][PATCH] bitbake: remove /usr from pseudo ignore paths Anton Kachalov
2021-01-07 22:16 ` [OE-core] " Richard Purdie
2021-01-08 0:56 ` Anton Kachalov [this message]
2021-01-08 8:26 ` Richard Purdie
2021-01-11 18:22 ` Peter Kjellerstedt
2021-01-15 17:04 ` Anton Kachalov
2021-01-15 17:09 ` Richard Purdie
2021-01-15 17:15 ` Richard Purdie
2021-01-15 19:54 ` Anton Kachalov
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='CADVsX89HCqKYNOyDMK1czkfaOw_TdrwVLK=bi_RanOKgDd=ZuQ@mail.gmail.com' \
--to=rnouse@google.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.