From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] remove neon from oe-core
Date: Wed, 10 Jun 2015 12:03:53 +0200 [thread overview]
Message-ID: <20150610100353.GA2400@jama> (raw)
In-Reply-To: <1554329.HKQRZb0eD9@peggleto-mobl.ger.corp.intel.com>
On Wed, Jun 10, 2015 at 10:17:53AM +0100, Paul Eggleton wrote:
> Hi Ross,
>
> On Tuesday 09 June 2015 20:14:15 Burton, Ross wrote:
> > Since Subversion moved away from neon it appears the only user of it in
> > oe-core is GStreamer as a HTTP client plugin. By virtue of being
> > maintained I suspect the libsoup plugin is generally the better choice
> > there, so as neon is now unmaintained upstream (last release September
> > 2014, doesn't work with latest GnuTLS release) I propose moving it to
> > meta-oe.
> >
> > Any comments?
>
> I have to be honest and say I don't like meta-oe continuing to be a dumping
> ground for old things that only a few (or no) people are using - if we must
> keep these recipes around, I'd rather they go into a different layer even if
> that layer's only grouping factor is "legacy items", at least then they are
> labelled appropriately. GStreamer 0.10 and BlueZ 4 were recent examples,
> perhaps I should have spoken up earlier, although I don't necessarily think
> it's too late.
>
> Martin - what do you think?
Yes, meta-legacy not included in my world builds looks much better than
dumping untested changes to meta-oe (both gstreamer-0.10 and bluez-4
dumps didn't even parse in form how they were sent to oe-devel ML).
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2015-06-10 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 19:14 [RFC] remove neon from oe-core Burton, Ross
2015-06-10 1:41 ` akuster808
2015-06-10 9:17 ` Paul Eggleton
2015-06-10 9:31 ` Burton, Ross
2015-06-10 10:03 ` Martin Jansa [this message]
2015-06-10 10:24 ` 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=20150610100353.GA2400@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.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