From: "Barros Pena, Belen" <belen.barros.pena@intel.com>
To: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: FW: Removing Hob for 2.1
Date: Mon, 29 Feb 2016 11:04:40 +0000 [thread overview]
Message-ID: <D2F9D639.7512C%belen.barros.pena@intel.com> (raw)
In-Reply-To: <2956615.y8hyrZheM7@peggleto-mobl.ger.corp.intel.com>
FYI
On 26/02/2016 03:49, "Paul Eggleton" <paul.eggleton@linux.intel.com> wrote:
>Hi folks,
>
>So we've been gearing up the Toaster web UI to replace the Hob (GTK+
>based) UI
>for some time now; Hob has basically been on life support for the past
>few
>releases. As of late last month in master, Toaster has the capability to
>select the packages in an image, removing the last thing that Hob could
>do
>that Toaster couldn't. This means it's about time we looked at removing
>Hob -
>particularly if we want to do so for the upcoming 2.1 release as we
>should
>really do so within the M3 development timeframe which is almost over.
>
>To recap, the reasons why Hob ought to be removed include:
>
>- The code is tightly woven into BitBake, making it fragile. This means
>it
>needs significant QA and maintenance on an ongoing basis.
>
>- Some of the implementation is not ideal; we'll be able to remove some
>cruft
>from BitBake and OE-Core at the same time.
>
>- It's GTK+ 2 based, not the current GTK+ 3.
>
>- Toaster is now a much more capable UI and is being actively maintained
>
>I'm maintaining a list of things we would drop together with Hob, so I
>could
>probably come up with a patchset - I just wanted to give people a heads
>up and
>double check that this is something we indeed want to do in 2.1. Any
>comments?
>
>Cheers,
>Paul
>
>--
>
>Paul Eggleton
>Intel Open Source Technology Centre
prev parent reply other threads:[~2016-02-29 11:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 2:49 Removing Hob for 2.1 Paul Eggleton
2016-02-26 2:54 ` [Openembedded-architecture] " Khem Raj
2016-02-26 19:15 ` Anders Darander
2016-02-26 13:37 ` Philip Balister
2016-02-26 14:26 ` nick
2016-02-28 20:42 ` Paul Eggleton
2016-02-26 14:29 ` nick
2016-02-29 12:29 ` Barros Pena, Belen
2016-02-29 0:17 ` Standalone image writer Paul Eggleton
2016-02-29 1:46 ` [Openembedded-architecture] " Khem Raj
2016-02-29 3:31 ` Trevor Woerner
2016-02-29 3:48 ` Gary Thomas
2016-02-29 7:12 ` Paul Eggleton
2016-02-29 11:27 ` Barros Pena, Belen
2016-02-29 19:52 ` Paul Eggleton
2016-02-29 20:05 ` Giordon Stark
2016-03-02 21:16 ` Paul Eggleton
2016-03-02 23:18 ` Andrei Gherzan
2016-02-29 20:13 ` Philip Balister
2016-02-29 11:04 ` Barros Pena, Belen [this message]
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=D2F9D639.7512C%belen.barros.pena@intel.com \
--to=belen.barros.pena@intel.com \
--cc=toaster@yoctoproject.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.