[FFmpeg-devel] [PATCH] Make configure use --enable-{in, out}dev=foo for enabling a single inoutdev

[Stefano Sabatini]

On date Saturday 2009-06-27 13:39:17 +0200, Stefano Sabatini encoded:
> On date Friday 2009-06-26 00:28:52 +0200, Stefano Sabatini encoded:
> > On date Tuesday 2009-06-23 01:11:08 +0200, Diego Biurrun encoded:
> > > On Tue, Jun 23, 2009 at 12:30:52AM +0200, Stefano Sabatini wrote:
> > > > On date Monday 2009-06-22 07:29:50 +0200, Reinhard Tartler encoded:
> > > > > M?ns Rullg?rd <mans at mansr.com> writes:
> > > > > 
> > > > > >> This is both cleaner and less confusing.
> > > > > >
> > > > > > No objections from me.  This will of course break configure-invoking
> > > > > > scripts, so users with such scripts may be displeased.  Any such users
> > > > > > care to comment?
> > > > > 
> > > > > Please document that change in Changelog or some more appropriate
> > > > > place. doc/APIchanges might not just fit here. Probably it should also
> > > > > go in the release notes of the next release.
> > > > 
> > > > Well we could add something like this in the Changelog:
> > > > 
> > > > - make configure select the input/output devices using
> > > >   --enable-{in,out}dev/--disable-{in,out}dev
> > > > 
> > > > otherwise we could rename 'APIChanges' -> 'InterfaceChanges' and fill
> > > > it not only with the API changes, but also with the
> > > > configuration/build and ff* tools interface changes (or alternatively
> > > > we could have a separated file for that, but that looks overkill).
> > > > 
> > > > I have a slight preference for the last proposal, after all the
> > > > Changelog is more used for enumerating the features added/dropped
> > > > rather than the interface changes.
> > > 
> > > Seconded, our changelog is rather sparse..
> > 
> > Updated, with a Changelog entry.
> 
> Ping? Is OK to use the Changelog for such changes?

If there are no objections I'm going to apply this in a few days.

Regards.
-- 
FFmpeg = Fast & Fostering Mystic Practical Enlightened Gadget