On 2012-12-17 15:18:52 +0100, Diego Biurrun wrote: > On Mon, Dec 17, 2012 at 12:43:35AM +0100, Janne Grunau wrote: > > On 2012-12-16 23:45:06 +0100, Diego Biurrun wrote: > > > > > > There are multiple ways to handle these more general components: > > > > > > - have avconv directly depend on some or all of them > > > > In configure or just for FATE_AVCONV? The second sounds reasonable > > My idea was to have avconv depend on them in configure. Otherwise you > can hardly run any tests...
avconv is not just a tool to run tests. Just to pick one of the more obvious examples: the md5 protocol has very few use cases besides testing. Disabling it and still using avconv is reasonable. Just let the avconv fate tests depend on them and use the configure switch to reenable things required for testing if testing is desired > > > - have a group of "FATE deps" that get enabled automatically > > > > what does that mean? making it impossible to disable the file protocol > > for example? > > It could be tied to avconv or tied to a configure switch. how is that different from the option above? Janne _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
