On Mon, May 16, 2022 at 6:55 PM Kevin Kofler via devel
<devel(a)lists.fedoraproject.org> wrote:
Jiri Vanek wrote:
> > This sounds fascinating. Can anyone share details about this? On the
> I'm aware of some codecs, which are built in Fedora, then the binary is
> sent to .. cisco(?), and if passed, they are repacked into all live
> fedoras.
OpenH264 is actually *not* part of Fedora, as Red Hat is not allowed to ship
it under the patent license, only Cisco is. So it gets built on the Fedora
Koji in an unpublished tag, shipped from there to Cisco, and Cisco releases
it in a third-party repository that is enabled by default in the Fedora
repository configuration (but can be disabled by the user, e.g., I have it
disabled because the FFmpeg H.264 decoder and the x264 encoder, both from
RPM Fusion, are simply the better H.264 implementations). That is a very
special arrangement that is due to patent issues.
I do not see how OpenJDK qualifies for such a special arrangement, and even
if it does, what you want is exactly the opposite of what OpenH264 is doing:
You want to get a build *into* Fedora repositories that is not built in the
respective Koji buildroot (it may be built in Koji, but you want to build it
once for all Fedora releases, so not in the release's buildroot), whereas
OpenH264 is actually built *in* the release's Koji buildroot and then
shipped *elsewhere*.
I want to make a very important clarification here: we build OpenH264
for *all* Fedora releases and have Cisco host those binary RPMs for
us. This arrangement means we are still making per-release builds and
releasing those back into Fedora.
--
真実はいつも一つ!/ Always, there's only one truth!