Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Remove GUPnP
Date: Mon, 21 Jan 2013 15:57:39 +0000	[thread overview]
Message-ID: <1358783859.14265.66.camel@ted> (raw)
In-Reply-To: <cover.1358782098.git.ross.burton@intel.com>

On Mon, 2013-01-21 at 15:29 +0000, Ross Burton wrote:
> GUPnP is great, but it's untested in oe-core.  It's now in meta-multimedia where
> it's been upgraded and live alongside companion projects such as dLeyna and
> Rygel.

There is a trend at the moment to remove things from OE-Core. That is
well and good but the question is where to draw the line. I do want to
ensure we keep at least some cross section of software in the core so
that the core can be stressed in a variety of environments.

I'm not saying gupnp shouldn't move out however I do want to figure out
what is going to stay in the core that we can test with. Obviously
things remaining the core really do need end user apps that we can
stress them with.

I was a little sad to see gthumb being removed for example as we now
have no image viewer in the core. It was also a larger gtk app so
stressed more of that side of the apis. I took the patches as it
probably does belong in meta-gnome. How do we test the various image
decoding libraries are in fact working though?

Food for thought...

Cheers,

Richard






  parent reply	other threads:[~2013-01-21 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 15:29 [PATCH 0/2] Remove GUPnP Ross Burton
2013-01-21 15:29 ` [PATCH 1/2] gupnp: remove, migrated to meta-multimedia Ross Burton
2013-01-21 15:29 ` [PATCH 2/2] packagegroup-sdk-gmae: remove GUPnP stack as it's no longer in oe-core Ross Burton
2013-01-21 15:57 ` Richard Purdie [this message]
2013-01-21 16:13   ` [PATCH 0/2] Remove GUPnP Burton, Ross

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=1358783859.14265.66.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox