[packman] Status of package MPlayer - is it dead already?

[Masaru Nomiya]

Hello,

In the Message; 

  Subject    : Re: [packman] Status of package MPlayer - is it dead already?
  Message-ID : <UMZZIT.9NNQELWA9JCZ at gmail.com>
  Date & Time: Thu, 30 Jul 2026 19:08:54 +0200

[BL] == Bjørn Lie <bjorn.lie at gmail.com> has written:


BL>  to., juli 30 2026 at kl. 17.58 +0200 +02:00:00 skrev Manfred Hollstein
BL>  <manfred.h at gmx.net> følgende:
[..']
BL>  > But, to be honest, MPlayer is a dead horse, isn't it? It hasn't seen a
BL>  > new release since over 4 years. Shouldn't we disable it for Tumbleweed
BL>  > at least? As long as it still builds for Leap, it can remain enabled for
BL>  > them, but the stunts I did with the libSvtAv1Enc3 and ffmpeg-6 fixes are
BL>  > overkill, aren't they?
BL>  > 
BL>  > What do others think? Should the stuff kept around and MPlayer gets
BL>  > deactivated after the next build failure, or should I disable it right
BL>  > away on Tumbleweed?

BL>  Arch have patches to allow it to build with ffmpeg-7/8, see link

BL>  https://gitlab.archlinux.org/archlinux/packaging/packages/mplayer

The MPlayer source code is structured to retrieve the corresponding
ffmpeg source code during the build process, so it does not require
external ffmpeg files.

In other words, it is designed to actively incorporate the source code
for necessary features that are released as OSS, and is intended to
run standalone. At least in Tumbleweed, it can be built in a way that
takes advantage of this design.

Best Regards.

--
┏━━┓彡  Masaru Nomiya                       mail-to: nomiya @ ab.auone-net.jp
┃＼／彡
┗━━┛	"To hire for skills, firms will need to implement robust and
	    	intentional changes in their hiring practices — and change is
	    	hard."
	  
        -- Employers don’t practice what they preach on skills-based hiring --