[packman] mpv _disabled_ (amongst other packages) in pmbs for openSUSE_Leap_42.2

Tomáš Chvátal tomas.chvatal at gmail.com
Wed Nov 16 21:56:12 CET 2016

Simply put we always should rely on the update system of openSUSE.

It works well for all and there is no technical reason for the multimedia
apps to be an exception.

If there are benefits for updating mpv anyone can open a bugreport or
create the update submission.

Benefit of this apporach is that suddenly my multimedia apps won't break
because someone happily updated something.



2016-11-16 18:24 GMT+01:00 Olaf Hering <olaf at aepfle.de>:

> Am 16.11.2016 um 17:18 schrieb Manfred Hollstein:
> > If you believe, m:a is not needed, what's the suggested proposal then?
> multimedia:apps is a devel project for at least a few apps in Factory.
> Its certainly ok to have its Leap repo enabled. But the downside is that
> multimedia:apps builds against multimedia:libs, which in turn is also
> a devel project. Soon it will happen that ffmpeg gets new SONAMEs and
> mpv will stop working because it links against OBS.
> There will be always some conflict between "having the latest" and
> "having a consistent system". The idea was to provide updates via the
> 42.2:Update project. In the case of mpv itself it might be ok to build
> it unconditionally in PMBS for all repos. A few packages have
> Requires: mpv (Essentials/baka-mplayer, Essentials/smplayer,
> Multimedia/selene, Multimedia/xt7-player-mpv).
> So what should be done with mpv? Provide always the variant from
> multimedia:apps via PMBS (linked against the given ffmpeg from PMBS),
> or should mpv be updated as needed via the Update channel?
> Olaf
> _______________________________________________
> Packman mailing list
> Packman at links2linux.de
> http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

More information about the Packman mailing list