| 1 | | OK. Thanks for the quick response. |
| 2 | | |
| 3 | | 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. |
| 4 | | |
| 5 | | 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. |
| 6 | | |
| 7 | | 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? |
| 8 | | |
| 9 | | 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? |
| | 1 | OK. Thanks for the quick response. Not sure how this can coexist with the ubiquitous ffmpeg* ports. I'll leave this for others to decide. |
