On Sat, Nov 10, 2012 at 11:45 AM, Martin Storsjö <[email protected]> wrote:
> On Fri, 9 Nov 2012, Diego Biurrun wrote: > > On Fri, Nov 09, 2012 at 02:42:38PM +0200, Martin Storsjö wrote: >> >>> On Fri, 9 Nov 2012, Martin Storsjö wrote: >>> >>> This makes sure minimal configurations such as >>>> "--disable-everything --enable-avconv" will enable the filters >>>> necessary for running avconv, instead of just keeping avconv >>>> disabled despite "--enable-avconv". >>>> --- >>>> configure | 6 +++--- >>>> 1 file changed, 3 insertions(+), 3 deletions(-) >>>> >>> >>> OTOH, this makes a plain --disable-everything configuration still >>> enable these filters (since avconv isn't disabled by >>> --disable-everything). >>> >> >> Do you also feel that --disable-everything should disable the programs? >> > > Not sure really, but if someone builds with plain --disable-everything > --enable-<some-component>, I think they'd find it odd to build a bunch of > filters as well. OTOH, they can explicitly do "--disable-everything > --disable-avconv" - perhaps that'd be good enough? > > If its called "disable-everything", i would expect it to disable everything. Intuitive is to do what it says on the box, and not require additional options to get it really to do what you would expect.
_______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
