[OE-core] Gstreamer packaging

[Phil Blundell]

On Wed, 2011-06-29 at 11:53 +0100, Richard Purdie wrote:
> Obviously you can make the recipe depend on good+bad+ugly but its less
> than ideal for build time reasons (esp. when considering dependencies)
> but also the reason that good/bad/ugly exist in the first place which is
> licensing. 

It's only -ugly which has licensing issues, and those same licensing
issues also mean that plugins don't tend to migrate to or from -ugly in
the same way as they do between the other packages.  So, if -good, -bad
and -base were combined in a single recipe, leaving -ugly separate, that
would solve about 90% of the current nuisance.

Dependency-wise, gst-plugins-good is the only one with a large stack of
DEPENDS.  If you assume that most people are probably going to need at
least one plugin from that package anyway, which I think is probably the
case in reality, then the dependency impact of combining -good, -bad and
-base in a single recipe would be fairly negligible.  (The only extra
dependencies you'd get from -bad would be libmusicbrainz, tremor and
librsvg.)

Of course, another way to attack the dependency stack problem would be
to combine the recipes and then be more aggressive about allowing
DISTROs to select only the plugins (and hence the dependencies) that
they want.  For example, I have long found it slightly annoying that
gst-plugins-good requires gtk+ and x11 at build time since I don't
actually use either of those libraries in my deployed system.

p.