Best practise for gstreamer plugins?

[Gustavo Niemeyer]

First thing I would do is include whatever you need inside the snap itself,
and get things working quickly.

Then, there are a few different ways you can move from there. The first one
is actually to do nothing.. the whole snap infrastructure (snapcraft,
snapd, uploads, downloads) is becoming delta-aware right now, which means
even if the total size is 100MB, you'll generally be dealing with only a
few megs.

Another option, once you're unhappy with that, is using a content interface
which allows sharing data across your snaps. This is a bit more complex, so
I wouldn't bother unless there are benefits you're looking for, other than
just size.



On Sat, Jan 21, 2017 at 11:01 AM, <l-snapcraft at znn.info> wrote:

> What is the best practise when working with gstreamer plugins?
>
> When packaging feedreader, an app with some video and music
> capabilities, i hit the problem that it calls gst-plugin-scanner which
> is not included in the package. So the application does not run.
>
>      (feedreader:26336): GStreamer-WARNING **: External plugin loader
> failed. This most likely means that the plugin loader helper binary was
> not found or could not be run. You might need to set the
> GST_PLUGIN_SCANNER environment variable if your setup is unusual. This
> should normally not be required though.
>
> What is the "snap way" of solving this? When i include gstreamer in the
> snap it will cross the 100MB mark.
>
> Thanks
>
> --
> Snapcraft mailing list
> Snapcraft at lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>



-- 

gustavo @ http://niemeyer.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20170123/b0af9313/attachment.html>