Content-Type: text/plain; charset=ISO-8859-1
On Sun, Jan 13, 2013 at 9:54 AM, Fritz Meissner wrote:
That is a shame then, but the cases of cdrecord and Mozilla are quite
different and not the fault of the Debian community.
Big changes to a distro ie swapping out a lib which many apps depend on for
a new one should really get voted on but I'm not aware that ever happened
here - I expect not.
Agreed - they should've aimed to keep the same commands as used by ffmpeg.
I've not tried using libav from cli yet so I can only hope they've
simplified its commands as ffmpeg was hardly the easiest command line
program to use but staying true to upstream would've still been the
preference on most I'm sure.
Content-Type: text/html; charset=ISO-8859-1
In all three of these examples it wasn't the fault of the Debian mainta=
iners that these alternate versions get used, it was the authors of the sof=
tware switching from Free a software license such as the GPL to one that th=
e Debian social contract no longer considers free or trying to enforce copy=
right on corporate logos or whatever.
I'm not aware that there was any licence c=
hange in the ffmpeg/libav situation ? It just seems to have been a personal=
ity and development style issue between maintainers. I hear that Debian'=
;s decision was based on the fact the Debian maintainer concerned was a mem=
ber of the libav camp, rather than any real technical issue.
That is a shame then, but the cases of cdrecord and M=
ozilla are quite different and not the fault of the Debian community.Big changes to a distro ie swapping out a lib which many apps depend on f=
or a new one should really get voted on but I'm not aware that ever hap=
pened here - I expect not.
I cannot speak about technical matters, but the change is extremely inc=
onvenient because of all the outside packages which are set up to call ffmp=
eg and now need to be hand-configured for libav (I'm talking about sett=
ing up subsonic to run on an Ubuntu 12.10 server here). And why the libav d=
evelopers need to change command line options is beyond me - the least they=
could have done is keep to the established ffmpeg formats. There seems to =
be no functional reason for it, just a desire to be different.
Agreed - they should've aimed to keep the sam=
e commands as used by ffmpeg. I've not tried using libav from cli yet s=
o I can only hope they've simplified its commands as ffmpeg was hardly =
the easiest command line program to use but staying true to upstream would&=
#39;ve still been the preference on most I'm sure.=A0