libav @ 11.4

[rbubley]

Libav is a fork of the libraries underpinning ffmpeg.

[rbubley]

Portfile

[kencu (Ken)]

I updated this to the current version 12.1 (sorry for the delay), but on installation it ran into a collision with ffmpeg-devel that also installs similar headers into ${prefix}/include/libavcodec/*.

Also, I see this port installs a collection of static libraries (*.a) rather than the dynamic libraries preferred by MacPorts.

I'm not certain how you might want to resolve these.. I guess it would be useful to hear about what this adds that ffmpeg doesn't, how the include file problem might be solved, and how to get dynamic instead of static libraries...

All the best, Ken

[kencu (Ken)]

I'll upload the portfile updated to 12.1 for those who might follow

[kencu (Ken)]

Portfile v12.1

[rbubley]

For the collision, I guess it needs 'conflicts ffmpeg ffmpeg-devel' added to the portfile.

[rbubley]

For dynamic rather than static, adding

configure.args --enable-shared --disable-static 

should do the trick.

[kencu (Ken)]

OK. Thanks for the quick response.

The fact that it lays in identically-named headers as ffmpeg into the same location and yet apparently provides a somewhat different service does cause some hesitation for people who try to make a large collection of ports try to work correctly together -- certainly an opportunity there for trouble - perhaps surmountable by marking them as conflicting, as you point out. I wonder if the headers and libraries shouldn't be moved into a different location, however, where you'd have to specifically go looking to find them.

As you're (hopefully!) more familiar with this than I, please help me understand it a bit more so I might see how to approach this.

Is this something that provides capabilities that ffmpeg doesn't provide? Would a user desire to have this installed in addition to ffmpeg, perhaps, or are this and ffmpeg really either/or types of tools?

Is the library component of this designed to be something that other software would build against, or is the value of this port really in the installed binaries, and the libraries are just to support those binaries?

[kencu (Ken)]

I think we can close this ticket, as I don't see this making it into MacPorts as it appears that ffmpeg provides all this provides, is aggressively maintained, and conflicts with this. Please update if you feel this is not correct.