search

ohei / winff

Automatically exported from code.google.com/p/winff
0 stars 0 forks source link

why no include a ffmpeg static into Winff? #192

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Avoid problems with presets 
2. a major control about formats
3. No necessary ffmpeg by the distribution

What is the expected output? What do you see instead?

Stability

What version of the product are you using? On what operating system?

Winff 1.5.0 Fedora 18 32bits

Please provide any additional information below.
I was making a new rpm for Fedora 18

Original issue reported on code.google.com by davidjeremias82 on 10 Mar 2013 at 11:02

GoogleCodeExporter commented 8 years ago 
Did it in windows. Not sure about linux. Would love to have fedora 18 package.

Original comment by bgg...@gmail.com on 13 Mar 2013 at 2:38

GoogleCodeExporter commented 8 years ago 
Static linking is against the philosophy of most (Linux) distributions. 
Furthermore, Winff is not actually linked, but just calls a ffmpeg/avconv 
binary and providing "convenience copies" is considered bad practice. 
Furthermore, maintaining a ffmpeg or avconv build ourselves just adds to our 
maintenance burden, where I don't think it is worth it. I personally will not 
provide them, but if anybody wants to do that, I won't object too loud.

For Fedora packages, please see our recent addition of providing packages 
tweaked towards specific Fedora versions at 
http://code.google.com/p/winff/wiki/FedoraInstallation

Original comment by poipodec...@hotmail.com on 17 Mar 2013 at 7:58