[OE-core] [RFC] remove neon from oe-core

[Martin Jansa]

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 at gmail.com