[OE-core] [PATCH 1/6] gstreamer1.0-plugin-base: Update packageconfigs

[Carlos Rafael Giani]

Back when I first wrote meta-gstreamer1.0, I made the decision to 
include packageconfigs for the two most used and most important set of 
layers, oe-core and meta-openembedded. Packageconfigs whose dependencies 
are in oe-core are enabled by default, those who aren't in oe-core but 
in meta-openembedded are disabled by default.

I did that because including packageconfigs for all sorts of layers made 
things complicated very fast. Plus, these two layers are kept up to date 
and are reviewed, which is not necessarily true for other layers. And, 
other layers may be much more specific to certain distros, BSPs, 
frameworks than these two.

Here's an example. libvisual is in meta-debian and meta-qt5-extra. Why 
should I have to include these much more specific layers to use a 
packageconfig that isn't specific to debian or qt5?

I'd actually prefer a libvisual recipe in meta-openembedded, with 
bbappens in these two layers to customize it for their needs.


On 2018-07-19 03:38, Anuj Mittal wrote:
> On 07/17/2018 05:35 PM, Carlos Rafael Giani wrote:
>> * There is no libvisual recipe in oe-core or in meta-openembedded, so
>>    the visual packageconfig needs to go
> What is the benefit of removing it as compared to just letting it be
> present as a configurable option which isn't enabled by default and is
> still valid? It might be needed by layers outside of
> oe-core/meta-openembedded ...
>
> It was added specifically in a commit and I see a recipe present when I
> search on layers.openembedded.org.
>
> Thanks,
>
> Anuj