From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
bitbake-devel@lists.openembedded.org
Cc: JPEWhacker@gmail.com
Subject: Re: [bitbake-devel][PATCH] cooker: Handle ImportError for websockets
Date: Fri, 21 Feb 2025 09:14:21 +0000 [thread overview]
Message-ID: <b78c624ef4f48bf9f4c8d571555dd693ea8da4de.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8LynhGChryLLHYFSz3=G70nO1938FwbfHN58rucuQ2sw@mail.gmail.com>
On Fri, 2025-02-21 at 10:11 +0100, Alexander Kanavin wrote:
> On Thu, 20 Feb 2025 at 17:05, Alexander Kanavin via
> lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
> wrote:
>
> > - we can extend bitbake-setup configurations with 'install-buildtoos:
> > true' parameter, and then use it in all official configurations that
> > need functional websockets to access pre-built sstate to always
> > install buildtools, even on systems where it's not actually necessary.
> >
> > None of these are great, but I'm leaning towards the last. Looking for
> > better ideas!
>
> Ok, I've slept on it, and concluded that bitbake-setup should simply
> always install buildtools by default. It's a front line tool for new
> users, and it can't afford to fail in mysterious ways. There will be a
> setting to turn it off, for those who know what they're doing and know
> they don't need buildtools.
I think that should be an option but I'm reluctant to say to use it by
default as we're just not going to find out about host issues until it
is too late. Our sanity tests are supposed to detect and give human
readable errors for the common issues you'd encounter.
Cheers,
Richard
next prev parent reply other threads:[~2025-02-21 9:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 18:35 [bitbake-devel][PATCH] cooker: Handle ImportError for websockets Joshua Watt
2025-02-20 16:05 ` Alexander Kanavin
2025-02-21 9:16 ` Richard Purdie
2025-02-21 16:07 ` Joshua Watt
2025-02-25 8:22 ` Alexander Kanavin
2025-02-25 10:11 ` Richard Purdie
2025-02-25 10:40 ` Alexander Kanavin
2025-02-25 10:52 ` Richard Purdie
2025-02-25 11:48 ` Alexander Kanavin
[not found] ` <1825F6393BB749ED.25123@lists.openembedded.org>
2025-02-21 9:11 ` Alexander Kanavin
2025-02-21 9:14 ` Richard Purdie [this message]
2025-02-21 12:18 ` Alexander Kanavin
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=b78c624ef4f48bf9f4c8d571555dd693ea8da4de.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=JPEWhacker@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=bitbake-devel@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.