On 4/19/2018 11:19 AM, Derek Buitenhuis wrote: > On 4/19/2018 11:40 AM, wm4 wrote: >> Regarding this patch, personally I don't think using getenv() to >> configure what is pretty much API semantics is acceptable. But a new >> API function that restricts what codecs are used based on a string >> argument might be ok. Then applications could use it to implement >> codec selection control via environment or command line arguments or >> something else. > > +1 no getenv
We've rejected other patches for this same reason before, so yeah, no changes that depend on environment variables. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
