Gentoo Archives: gentoo-dev

From: Rich Freeman <rich0@g.o>
To: gentoo-dev <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] Last rites: media-video/mplayer2 media-video/smplayer2
Date: Mon, 16 Mar 2015 14:27:27
Message-Id: CAGfcS_ne5TU1Hg_A4AktJ_WwYf9tvumfOQNHp_CftpLUFGhOPQ@mail.gmail.com
In Reply to: Re: [gentoo-dev] Re: [gentoo-dev-announce] Last rites: media-video/mplayer2 media-video/smplayer2 by Ben de Groot
1 On Mon, Mar 16, 2015 at 10:09 AM, Ben de Groot <yngwin@g.o> wrote:
2 > On 16 March 2015 at 21:54, Юра Цимбалов <yura.tsts@×××××.com> wrote:
3 >>> That would be great, but it depends on getting newer mpv stable, while
4 >>> (s)mplayer2 is dead and broken right now.
5 >>
6 >> https://bugs.gentoo.org/buglist.cgi?quicksearch=mplayer2&list_id=2703540
7 >>
8 >> Why it's broken?
9 >
10 > As stated in my original message: See bugs 452484, 485994, 512082, 519212.
11 >
12
13 Obviously if software has serious issues it needs to be treecleaned,
14 but I seem to recall this package coming up in the whole ffmpeg
15 defaults discussion.
16
17 As I recall libav is now the default, and the argument was that users
18 should just use mplayer2 and such for compatibility. Now it sounds
19 like stable users don't have that option, at least for a time.
20
21 This won't affect established users since I suspect 95% of them never
22 switched away from ffmpeg in the first place and if they did they'll
23 just start mixing keywords, but I imagine that this sort of thing will
24 be confusing at best for a new user. If mplayer is the first package
25 they install they'll probably get told to fix their USE flags and be
26 fine. If they first install something else that works with libav I
27 imagine things will get more confusing when they go to install
28 something like mplayer.
29
30 I'm not saying that we need to keep mplayer2 around. I'm just saying
31 that we should be thinking about whether stuff like this makes the
32 Gentoo learning curve unnecessarily steep and what can be done to
33 mitigate it. I'd really love it if we could eventually get some kind
34 of automated CI testing that just starts with a stage3 and all
35 defaults and tries to emerge a few key packages (kde on the kde
36 profile, gnome on the gnome profile, maybe xfce and a browser on the
37 default profile - the goal is to just pull in a bunch of very
38 common/generic stuff). I occasionally do this in a chroot and on
39 occasion I'm a bit surprised by the results, but I haven't done this
40 too recently.
41
42 --
43 Rich

Replies