Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Replacing Web in Sato with Midori
Date: Wed, 08 Aug 2012 13:23:08 +0100	[thread overview]
Message-ID: <1344428588.9756.333.camel@ted> (raw)
In-Reply-To: <5995DE95-9135-4B8E-82BA-F0938B2D755F@dominion.thruhere.net>

On Wed, 2012-08-08 at 12:01 +0200, Koen Kooi wrote:
> Op 8 aug. 2012, om 10:41 heeft "Burton, Ross" <ross.burton@intel.com> het volgende geschreven:
> 
> > Hi,
> > 
> > As everyone who's used it can attest, Web (the optional browser in
> > Sato) is pretty rough.  Part of my plans about replacing Sato with a
> > leaner environment involves replacing it with Midori, and if there
> > isn't any disagreements I'll work on a submission to merge Midori into
> > Sato now for everyone who expects the Sato web browser to be useful.
> > 
> > This will involve pulling a few projects from meta-oe to oe-core:
> > ca-certificates, python-docutils and vala specifically (although its
> > possible that we can drop the vala dependency).
> 
> Adding more stuff to oe-core is a bad idea. You should take this
> opportunity to split all the sato stuff into its own layer.

I feel very strongly that having a core layer with no way of
demonstrating and testing it is a very bad idea. I haven't changed my
mind about this and am very unlikely to. "How do you know it works?" is
the question you ask about package upgrades for example.

I know Ross is planning to rationalise what is in sato and ultimately
replace it with something more suited to this purpose. I don't think
removing it entirely is a good move.

One of the steps involved here is to replace what is currently a rather
hacky browser with a real world usable one which fulfils the above
objective - allow OE-Core to be testable. "web" is a core technology and
important to a significant subset of devices. So some things need to get
added, some will also get removed and things will become much less
"sato" like over time.

For example, pimlico is likely just to get removed/moved out to
meta-gnome or wherever as PIM isn't core technology like web is.

So I'd like to give Ross some room to manoeuvre and try to improve this.
It will involve some additions, deletions will also happen. I for one
think this proposal is a good first step (of many).

Cheers,

Richard






  reply	other threads:[~2012-08-08 12:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08  8:41 Replacing Web in Sato with Midori Burton, Ross
2012-08-08 10:01 ` Koen Kooi
2012-08-08 12:23   ` Richard Purdie [this message]
2012-08-08 12:36     ` Martin Jansa
2012-08-08 12:48       ` Richard Purdie
2012-08-09 15:18         ` Martin Jansa
2012-08-08 13:56       ` Koen Kooi
2012-08-08 14:03         ` Paul Eggleton
2012-08-08 14:47           ` Koen Kooi
2012-08-08 15:00             ` Paul Eggleton
2012-08-08 15:04               ` Samuel Stirtzel
2012-08-08 15:07                 ` Paul Eggleton
2012-08-08 10:39 ` Phil Blundell
2012-08-08 12:07   ` Burton, Ross
2012-08-08 12:26     ` Phil Blundell
2012-08-08 12:31       ` Burton, Ross
2012-08-08 12:28   ` Richard Purdie
2012-08-08 16:39   ` Mark Hatle

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=1344428588.9756.333.camel@ted \
    --to=richard.purdie@linuxfoundation.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