Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] I've written a filter in Rust
Date: Thu, 27 Feb 2025 23:40:42 +0100
Message-ID: <20250227224042.GI4991@pb2> (raw)
In-Reply-To: <DM8P223MB0365DB9CBF78332CD8F36575BAC22@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>


[-- Attachment #1.1: Type: text/plain, Size: 2089 bytes --]

Hi

On Wed, Feb 26, 2025 at 04:35:52PM +0000, Soft Works wrote:
[...]
> 
> > What we could do is make it easier to build from source with extra
> > components:
> 
> [..]
> 
> 
> > - Build scripts that detect available libraries. Possibly build scripts
> >   that install devel packages for these libraries. Possibly even a build
> >   script that installs a Debian in a VM/container.
> > 
> > - Tweak the build system to let add a component by just dropping it in a
> >   subdirectory.
> 
> Yes, that's exactly what I mean. Currently, when adding custom filters
> (or codecs, muxers etc.), you need to make changes at various places
> and each time when rebasing or merging things around and managing
> versions, these things are causing conflicts.
> Or when you want to provide a filter/component to the community 
> (as source code), you can't provide a patch that could be applied to
> arbitrary ffmpeg versions.
> 
> Having a "plugins" directory that is automatically scanned for plugin
> code, or a command line parameter like
> 
> ./configure --plugindir=../myplugins
> 
> would be fine IMO.
> 
> And obviously much more agreeable for everybody than runtime
> plugins, even though I would favor having both 😊

ffmpeg-source-plugins/

And i would suggest to instead of the source, also to allow
files in that directory listing where to find the source

source-plugin speech2subtile
url https://github.com/someone/somerepo/tree/$PLUGIN_VERSION or https://someplace/speech2subtile.$PLUGIN_VERSION.tar.gz(.sig)
gpg-key-fingerprint 24CE01CE9ACC5CEB74D88D9DB063D99736E54C93

that then could download a release tarball, and signature
get the gpg key from the key fingerprint
check the tarball to be authentic
and extract

This is simple (like 5 lines of code) and allows plugin authors to
update their plugins without everyoen having to re-download.


thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Republics decline into democracies and democracies degenerate into
despotisms. -- Aristotle

[-- 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".

  reply	other threads:[~2025-02-27 22:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 13:06 Leandro Santiago
2025-02-20 16:20 ` Leandro Santiago
2025-02-20 22:49 ` Michael Niedermayer
2025-02-21  7:56   ` Leandro Santiago
2025-02-21  9:01   ` Tomas Härdin
2025-02-21  9:21     ` Soft Works
2025-02-21 13:21     ` Michael Niedermayer
2025-02-21 14:30       ` Soft Works
2025-02-21 14:53         ` Kieran Kunhya via ffmpeg-devel
2025-02-21 15:02           ` Soft Works
2025-02-21 19:27             ` Kieran Kunhya via ffmpeg-devel
2025-02-21 20:10               ` Soft Works
2025-02-26 13:50                 ` Tomas Härdin
2025-02-26 14:18                   ` Zhao Zhili
2025-02-26 15:32                     ` Rémi Denis-Courmont
2025-02-26 16:03                       ` Zhao Zhili
2025-02-26 16:25                         ` martin schitter
2025-02-26 14:07                 ` Nicolas George
2025-02-26 16:35                   ` Soft Works
2025-02-27 22:40                     ` Michael Niedermayer [this message]
2025-02-21 16:39           ` Stephen Hutchinson
2025-02-26 14:25         ` Vittorio Giovara
2025-02-21 13:18 ` Lynne
2025-02-21 13:44   ` Kieran Kunhya via ffmpeg-devel
2025-02-21 18:02   ` Tomas Härdin
2025-02-22 12:57     ` Rémi Denis-Courmont
2025-02-23 21:30       ` Tomas Härdin
2025-02-23 21:51         ` Michael Niedermayer
2025-02-26 14:11           ` Tomas Härdin
2025-02-27 21:01             ` Michael Niedermayer
2025-02-28  1:57               ` Pavel Koshevoy
2025-02-28 15:35               ` Rémi Denis-Courmont
2025-02-24 14:51         ` Rémi Denis-Courmont
2025-02-26 14:34           ` Tomas Härdin
2025-02-26 15:13           ` Leandro Santiago
2025-02-22 12:49   ` Rémi Denis-Courmont

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=20250227224042.GI4991@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