From: Joshua Lock <josh@linux.intel.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [bitbake-devel] Feedback on HOB (new image creator GUI)
Date: Fri, 30 Sep 2011 10:34:54 -0700 [thread overview]
Message-ID: <1317404099.11645.21.camel@scimitar> (raw)
In-Reply-To: <CAEsOVNdwudRO7V2DQhpESC=xCqDtJqxJ72+e_hYDLq7bE=z+cg@mail.gmail.com>
On Fri, 2011-09-30 at 10:20 -0600, McClintock Matthew-B29882 wrote:
> On Fri, Sep 30, 2011 at 9:36 AM, Yu Ke <ke.yu@intel.com> wrote:
> > Hi,
> >
> > As you may already know, a new GUI has been added to bitbake recently, i.e.
> > HOB (Human Oriented Builder). It is a graphical image creator that allows
> > user to freely choose which packages to be built in the image. The wiki
> > https://wiki.yoctoproject.org/wiki/BitBake/GUI/Hob has more detail.
> >
> > This email is to collect your feedback on the HOB. Current HOB is our first
> > version, and it surely has many place to improve. We has the plan to enhance
> > it in Yocto 1.2. So we really hope that you can use it and provide your
> > valuable feedback . We do think user's feedback/requirement is the right way
> > to go. Looking forward your valuable input.
> >
> > Best Regards
> > Ke
> >
> > Ps. The simple way to run hob is:
> > # touch conf/hob-pre.conf conf/hob-post.conf
> > # bitbake -u hob -r conf/hob-pre.conf -R conf/hob-post.conf
> >
> > Where conf/hob-pre.conf conf/hob-post.conf is the configuration file, which
> > can be empty in above case.
>
> Has any discussion gone into making some sort of plugin or extensions?
> I'd like for it to be as easy as possible for someone new to make hob
> be able to some things like: configure runtime services, configure
> networking settings, add users, and I'm sure there are other things.
No such discussion has occurred. These are good feature suggestions,
I'm not sure about a plugin mechanism - are you suggesting that
to enable the features mentioned or in addition to?
At least for enabling runtime services there's likely an issue of the
UI having enough knowledge of the init system to do so.
I can certainly see at least the three features proposed here being
desirable and I'll probably file those as feature enhancements in the
bugzilla, unless you'd like to?
Any further thoughts on customisations to enable via the GUI?
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-09-30 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 14:36 Feedback on HOB (new image creator GUI) Yu Ke
2011-09-30 15:49 ` Joshua Lock
2011-09-30 16:32 ` Koen Kooi
2011-09-30 17:16 ` [bitbake-devel] " Joshua Lock
2011-09-30 18:43 ` Koen Kooi
2011-10-01 0:30 ` Yu, Ke
2011-09-30 16:20 ` [bitbake-devel] " McClintock Matthew-B29882
[not found] ` <1317403442.11645.17.camel@scimitar>
2011-09-30 17:32 ` McClintock Matthew-B29882
2011-09-30 17:34 ` Joshua Lock [this message]
2011-09-30 21:55 ` Gary Thomas
2011-10-01 0:23 ` Yu, Ke
2011-10-01 17:46 ` Otavio Salvador
2011-10-01 17:51 ` Koen Kooi
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=1317404099.11645.21.camel@scimitar \
--to=josh@linux.intel.com \
--cc=B29882@freescale.com \
--cc=bitbake-devel@lists.openembedded.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox