From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/libx264: bump minimum required version to 160
Date: Thu, 11 Apr 2024 01:17:25 +0200
Message-ID: <20240410231725.GT6420@pb2> (raw)
In-Reply-To: <CA+anqdxuRWrvYwfQ4oADVq8rsj-Kg0CY0muUkj_U+h_JaC3WsQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2382 bytes --]
On Wed, Apr 10, 2024 at 03:30:23PM +0200, Hendrik Leppkes wrote:
> On Wed, Apr 10, 2024 at 3:19 PM Michael Niedermayer
> <michael@niedermayer.cc> wrote:
> >
> > On Tue, Apr 09, 2024 at 02:53:28PM +0200, Niklas Haas wrote:
> > > On Sat, 06 Apr 2024 22:28:26 +0200 Michael Niedermayer <michael@niedermayer.cc> wrote:
> > > > On Fri, Apr 05, 2024 at 07:44:52PM +0200, Niklas Haas wrote:
> > > > > From: Niklas Haas <git@haasn.dev>
> > > > >
> > > > > This version is four years old, and present in Debian oldstable, Ubuntu
> > > > > 22.04 and Leap 15.1.
> > > >
> > > > Ubuntu 20.04 has general support till 2025-05-29
> > > > Ubuntu 18.04 has security support (ESM) till 2028-04
> > >
> > > I'll relax it from 160 back down to version 155 then. That covers Ubuntu
> > > 20.04 and Debian oldoldstable.
> >
> > 18.04 has 152
> >
> > libx264-dev/bionic,now 2:0.152.2854+gite9a5903-2 amd64 [installed]
> >
> > Ubuntu 18.04 still has security support in ESM and ubuntu pro IIUC till 2028-04
> >
>
> Then they can use security updates from old release branches. The
> assumption that people will run Git ffmpeg but distribution provided
> x264 seems flawed. They can update dependencies that are important for
> them.
I use distribution provided packages unless i have a reason to do otherwise
If i have no such reason every case where thats not wroking is extra work
also if i take what you say litterally, then you provide an
argument to drop support for every distribution and require
every dependency to be from git head. I dont think you intended
that and i dont think that would be a good idea.
Maybe its just me but i find it desireable to be able to just
pull ffmpeg master head, build it and have it work on as many systems
as possible.
If for some reason a user needs git master of FFmpeg that doesnt mean
she needs anything else to be very recent.
You suggest people should just use release branches to get security updates
truth is, our release branches are sometimes behind git master
also we dont support releases. If someone finds a bug we demand reports
against git master.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Complexity theory is the science of finding the exact solution to an
approximation. Benchmarking OTOH is finding an approximation of the exact
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-04-10 23:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 17:44 Niklas Haas
2024-04-06 20:28 ` Michael Niedermayer
2024-04-09 12:53 ` Niklas Haas
2024-04-10 13:18 ` Michael Niedermayer
2024-04-10 13:30 ` Hendrik Leppkes
2024-04-10 23:17 ` Michael Niedermayer [this message]
2024-04-11 10:01 ` Nicolas George
2024-04-11 21:05 ` Vittorio Giovara
2024-04-10 13:47 ` Niklas Haas
2024-04-10 23:32 ` Michael Niedermayer
2024-04-11 22:55 ` Sean McGovern
2024-04-12 10:43 ` Tomas Härdin
2024-04-12 11:45 ` Michael Niedermayer
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=20240410231725.GT6420@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git