On Wed, Nov 14, 2012 at 11:35:17AM +0000, Måns Rullgård wrote:
> Diego Biurrun <di...@biurrun.de> writes:
> > On Sat, Nov 10, 2012 at 03:34:22PM +0000, Måns Rullgård wrote:
> >> Diego Biurrun <di...@biurrun.de> writes:
> >> > On Sat, Nov 10, 2012 at 03:05:08PM +0000, Måns Rullgård wrote:
> >> >> Diego Biurrun <di...@biurrun.de> writes:
> >> >> > This better describes what the option actually does.
> >> >> > --- a/configure
> >> >> > +++ b/configure
> >> >> > @@ -130,7 +130,7 @@ Component options:
> >> >> >
> >> >> >  Individual component options:
> >> >> > -  --disable-everything     disable all components listed below
> >> >> > +  --disable-components     disable all components listed below
> >> >> >    --disable-encoder=NAME   disable encoder NAME
> >> >> >    --enable-encoder=NAME    enable encoder NAME
> >> >> >    --disable-encoders       disable all encoders
> >> >> > @@ -1946,7 +1946,7 @@ for opt do
> >> >> > -    --disable-everything)
> >> >> > +    --disable-components)
> >> >> >      map 'eval unset \${$(toupper ${v%s})_LIST}' $COMPONENT_LIST
> >> >> >      ;;
> >> >> 
> >> >> I don't think this name is particularly accurate either.
> >> >
> >> > Suggestions?  "components" is how we refer to individual muxers, decoders
> >> > and whatnot in the code, at least in the build system, when we need an
> >> > umbrella term.
> >> 
> >> "Component" could mean just about anything.  What you choose to call by
> >> that name is far from obvious to a casual user.
> >
> > A term that covers encoders, decoders, hwaccels, muxers, demuxers,
> > parsers, bsfs, protocols, indevs, outdevs, devices and filters will by
> > necessity end up being generic and only have meaning in context.
> 
> It would be perfectly logical to assume it means one of the libav*
> libraries.

So?  How about we move this discussion in a constructive direction of
how things should look like instead of just enumerating problems in
proposed alternatives?

currently:

  --disable-everything

which does not do what the name implies.

proposal:

  --disable-programs (useful for library-only builds)
  --disable-libraries (avoids confusion about --components semantics)
  --disable-components (--everything renamed)
  --disable-subcomponents (alternative naming for --components)
  --disable-everything (all of the above)

I have most of this either in patches on the ml or implemented locally.

Diego
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to