How difficult would it be to create a similar package for libav?

[antoineMoPa]

Hi @eugeneware!

As you may know, ffmpeg is built of some libraries (libav*) - which can be useful on their own.

I'm currently manually managing libav dependencies in a node project (the project is using beamcoder) and I was wondering if packaging these libs as a node package would make sense.

Also, I wonder if this would this be a good fit for this project? Currently, it looks like ffmpeg-static ships a ffmpeg binary with all the libs already statically-linked. Maybe ffmpeg-static could ship a smaller ffmpeg executable with the libraries alongside - Probably the size would be similar, but we would gain the possibility of using beamcoder (and any other lib that might work with libav).

[derhuerst]

I have adapted the changes in #113 in the ffprobe branch (permalink). With these changes, we can publish any number of *-static "distribution packages" from this repo, as long as the download script can provide their binaries/files. We could definitely add another "distribution package" for libav libs (although the -static naming wouldn't make sense in this case)!

What do you think?