Comment # 7 on bug 4363 from
(In reply to Nicolas Chauvet from comment #5)
> Having a more deep look into your packages, it's seems like you are
> replacing the media sub-package to complement the fedora chromium version.
> So it's by design that you "substitute" the fedora -media version with a
> freeworld version.
> Unfortunately, the substitute methods imply to conflict with the fedora
> -media package having them removed before the freeworld version can be
> installed.
> If that's easy enough in command line, it will be more difficult to do with
> any software center application.
> So I'm trying to reword my question:
> - Is there any reason the fedora chromium -media subpackage is shipped for
> anything useful ? Is it possible to exclude
> /usr/lib64/chromium-browser/ from chromium-libs-media , make
> /usr/lib64/chromium-browser/ dlopen if available
> from our -freeworld package ?
> Or even better, make the dlopen ffmpeg-libs if available making
> any chromium-*freeworld package unneeded ? (like what is done with firefox
> currently dlopening ffmpeg-libs at runtime).

(In reply to Rex Dieter from comment #6)
> My understanding is:  No that is not possible.  What is proposed in the
> original packaging here is (currently) the only/best way.

Indeed, from what I can see, there are only two options:
- Add a chromium-freeworld package, which could be made conflict-free by
removing chrome-remote-desktop and reworking the fedora spec a bit.
- The current method of having a libs-media-freeworld package that replaces and
provides libs-media.

I don't believe that there's any other way of handling it.

I was going to spend some time today to update it, but if this is a blocking
issue, I can hold off until we can sort it out.

You are receiving this mail because: