From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "chris.laplante@agilent.com" <chris.laplante@agilent.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Cc: "behanw@converseincode.com" <behanw@converseincode.com>
Subject: Re: [bitbake-devel] Online tool for playing with variable expansion - first steps and where to host it
Date: Thu, 15 Feb 2024 17:23:44 +0000 [thread overview]
Message-ID: <7ea7dc754fda197b9f911bb287b1398114dfc0c1.camel@linuxfoundation.org> (raw)
In-Reply-To: <DM8PR12MB5430121AAE8FABC5D834CF8F8B4D2@DM8PR12MB5430.namprd12.prod.outlook.com>
On Thu, 2024-02-15 at 15:29 +0000, chris.laplante@agilent.com wrote:
> > > I'll do unless people feel strongly otherwise. (I'd rather not put it
> > > in BitBake itself since due to CORS restrictions I'll probably need to
> > > keep tar.gz copies of BitBake in the repo so the client can fetch it
> > > (*3). I also don't think we want all the webpack and TypeScript
> > > clutter in BitBake)
> >
> > I agree it doesn't belong in bitbake itself. I did wonder about something like the
> > yoctoproject github if you wanted more exposure there but I don't have a strong
> > preference either way.
>
> I also don't have a strong preference. I envision eventually I'll add little "Run"
> links in the BitBake manual next to code samples, especially in the chapter on
> variable overrides, which will take the reader directly to the playground. So
> I think no matter where we host it, people will eventually find it.
That does potentially change things a little as if we want to make
links from the official project docs, putting it somewhere with our
other project repos does start to make sightly more sense.
I say that as people do move on and do other things and we'd have no
way to recover other than changing the links in that case, which we can
only do with the newer versions, not retrospectively.
> > No objection, I mainly wanted to reply to show someone read it and thought it
> > sounds fun :)
>
> Thank you :)!
>
> One more question - what to name it? I was tentatively calling it bitodide,
> but I kind of hate the name. I think "BitBake Playground" is the obvious
> choice. Could also do "BitBake Explorer" (ala Compiler Explorer). But I think
> I like Playground better...
I prefer Playground fwiw.
Cheers,
Richard
next prev parent reply other threads:[~2024-02-15 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 16:59 Online tool for playing with variable expansion - first steps and where to host it chris.laplante
2024-02-15 15:20 ` [bitbake-devel] " Richard Purdie
2024-02-15 15:29 ` chris.laplante
2024-02-15 17:23 ` Richard Purdie [this message]
2024-02-15 17:25 ` chris.laplante
2024-02-15 17:28 ` Richard Purdie
2024-02-16 13:46 ` chris.laplante
2024-05-13 14:55 ` BB Datastore Playground preview is now live chris.laplante
2024-05-13 16:06 ` Michael Halstead
2024-05-13 16:19 ` chris.laplante
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=7ea7dc754fda197b9f911bb287b1398114dfc0c1.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=behanw@converseincode.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=chris.laplante@agilent.com \
/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.