public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [PATCH] ffmpeg-compat.eclass: new eclass
Date: Tue, 11 Mar 2025 04:37:50 -0000 (UTC)	[thread overview]
Message-ID: <pan$3c5b4$22e4ff72$9366dbd4$8be0c105@cox.net> (raw)
In-Reply-To: Z83tW7LbwTXZrqWg@eversor

Ionen Wolkens posted on Sun, 9 Mar 2025 15:34:51 -0400 as excerpted:

> On Sat, Mar 08, 2025 at 10:34:31PM -0500, Ionen Wolkens wrote:
>> Sending this to dev ML in advance given it's simple and "probably"
>> won't need to change the code further.

So the will-be-slot tracker bugs may in the (long) bug list at the bottom 
of the PR, but I didn't see them specifically named either here or in the 
PR.  In the interest of preventing duplicated effort here's what I found

https://bugs.gentoo.org/831437  ffmpeg-5 (4 compat)

One remaining open bug.  media-sound/moc.  Latest in-tree is a 2016 
alpha.  There are active users and newer overlay versions with ffmpeg-6 
compat at least.  Alternatives are killing USE=ffmpeg or last-riting.

Bottom line:  As the PM says a 4-compat slot is likely to be short-lived.

https://bugs.gentoo.org/901257  ffmpeg-6.0 (5 compat)

Again just one open bug, and shorter list in general.  But that bug is 
media-libs/gegl (gimp dep).  Test not build failure and upstream 
apparently says no big deal.  Again killing USE=ffmpeg is one (bad?) 
alternative.  From the bug it's almost good with ffmpeg-7 (one remaining 
test failure.)

Bottom line:  An ffmpeg-6 compat slot /could/ be short-lived as well, and 
if not, certainly the slot should indeed be very limited usage (gegl only 
unless something else pops up).

https://bugs.gentoo.org/928905  ffmpeg-7.0 (6 compat, deps on the above 
two also)

As might be expected ffmpeg-7 still has a decent number of open bugs, tho 
a scan suggests ~2/3 are fixed already.  The 6-compat slot would thus get 
more usage including (as of my last sync) both xine-lib and mplayer latest 
(non-live) in-tree, so many users will likely need it.

>> If interested in the whole deal, see the PR instead:
>> https://github.com/gentoo/gentoo/pull/40942
> On a side-note, the ffmpeg ebuild was also rewritten in that PR which
> may be of more interest than the slotting to some.

> See the `rewrite live ebuild` commit message if want details, some
> changes are debatable and may anger some users, albeit I'm mostly aiming
> for stabler ffmpeg.

Having looked over that live ebuild commit message, LGTM; yes a bunch of 
changes but no "anger some users" here! =:^)

(FWIW I'm on ffmpeg-live (due to firefox/youtube stalls on the last 
release I checked that are fixed in live) and seem to have 1/2-2/3 the USE 
flag changes set already.  I'll likely set the others on next update (as 
you surely already know the ffmpeg-live commit-stream's a firehose so it's 
a virtually guaranteed smart-live-rebuild), whether the rewrite's in-tree 
or not by then.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



  reply	other threads:[~2025-03-11  4:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-09  3:34 [gentoo-dev] [PATCH] ffmpeg-compat.eclass: new eclass Ionen Wolkens
2025-03-09 10:17 ` James Le Cuirot
2025-03-09 10:27   ` Ionen Wolkens
2025-03-09 10:33     ` James Le Cuirot
2025-03-09 15:22       ` Ionen Wolkens
2025-03-09 16:45 ` Eli Schwartz
2025-03-09 18:47   ` Ionen Wolkens
2025-03-09 19:34 ` Ionen Wolkens
2025-03-11  4:37   ` Duncan [this message]
2025-03-11  5:14     ` [gentoo-dev] " Ionen Wolkens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='pan$3c5b4$22e4ff72$9366dbd4$8be0c105@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox