From: "Rémi Denis-Courmont" <remi@remlab.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] SDR lib comments
Date: Fri, 29 Sep 2023 16:29:39 +0300
Message-ID: <320C8E15-9097-41DD-A0F7-FF6B06422859@remlab.net> (raw)
In-Reply-To: <ZRa4T9uW5VBw9HQ7@phare.normalesup.org>
Le 29 septembre 2023 14:43:11 GMT+03:00, Nicolas George <george@nsup.org> a écrit :
>Anton Khirnov (12023-09-29):
>> What does anybody gain from it being in our source tree, as opposed to a
>> separate library?
>
>Not having to maintain yet another packaging and build system.
Talk about flimsy "scraps of the bottom of the barrel" reasons.
Considering the accumulated cruft in the FFmpeg build system, this is more of a reason *not* to share source trees - rationalise the build system (or use an off-the-shelf one, whatever rocks your boat).
>Not having an external dependency for something that could be considered
>a core feature.
A core feature that depends on niche hardware, and is only supported on a narrow subset of target platforms. Oxymoronic much?
If those are your reasons, you'd have better kept them to yourself, because they're frankly ridiculous.
Normally you'd bundle things because they are tightly coupled. But if they were tightly coupled, then there would be maintenance costs, so that's also a self-defeating argument.
_______________________________________________
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:[~2023-09-29 13:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 16:43 Michael Niedermayer
2023-09-28 10:28 ` Anton Khirnov
2023-09-28 19:28 ` Michael Niedermayer
2023-09-28 21:05 ` Rémi Denis-Courmont
2023-09-28 22:18 ` Michael Niedermayer
2023-09-29 7:03 ` Nicolas George
2023-09-29 8:23 ` Rémi Denis-Courmont
2023-10-02 10:08 ` Nicolas George
2023-09-29 8:34 ` Rémi Denis-Courmont
2023-10-02 10:06 ` Nicolas George
2023-09-29 12:59 ` Vittorio Giovara
2023-10-02 10:05 ` Nicolas George
2023-09-28 21:07 ` Vittorio Giovara
2023-09-28 22:58 ` Michael Niedermayer
2023-09-29 9:43 ` Anton Khirnov
2023-09-29 11:43 ` Nicolas George
2023-09-29 13:29 ` Rémi Denis-Courmont [this message]
2023-09-29 13:53 ` Nicolas George
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=320C8E15-9097-41DD-A0F7-FF6B06422859@remlab.net \
--to=remi@remlab.net \
--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