[MPlayer-cvslog] CVS: main configure,1.1197,1.1198

[Ivan Kalvachev]

2006/5/14, The Wanderer <inverseparadox at comcast.net>:
> Ivan Kalvachev wrote:
>
> > 2006/5/13, Diego Biurrun <diego at biurrun.de>:
> >
> >> On Sat, May 13, 2006 at 09:25:14PM +0300, Ivan Kalvachev wrote:
>
> >>> Then how is user supposed to request auto detection if option is
> >>> disabled by default?
> >>
> >> There is (currently) no way to request autodetection.
> >
> > !
>
> I'm not sure why you're surprised to learn this... *have* you in fact
> been around for the past 'you people should change --enable to mean
> "autodetect"' threads, or is my memory being unreliable again?

Well, here is Diego agreeing with my current arguments, from an very
ancient thread:
http://article.gmane.org/gmane.comp.video.mplayer.devel/14823


Here is incomplete list of previous configure flames.
http://news.gmane.org/find-root.php?group=gmane.comp.video.mplayer.devel&article=3279
http://news.gmane.org/find-root.php?group=gmane.comp.video.mplayer.devel&article=14531
http://news.gmane.org/find-root.php?group=gmane.comp.video.mplayer.devel&article=13206
http://news.gmane.org/find-root.php?group=gmane.comp.video.mplayer.devel&article=20350
http://news.gmane.org/find-root.php?group=gmane.comp.video.mplayer.devel&article=27349

The current struggle is caused by the reversal that Diego made,
claiming that it breaks the "semantics". My claims are:
1. there is no such "semantics"
2. it is harmful for the users.


Rereading the maillist, it seems that I'm the only one that claims
default-disabled options are autodetected, but on the other hand
nobody claimed I'm wrong.
No surprise that I assumed the most logical option for correct, giving
that there are disabled options that DO execute checks when --enabled.


Anyway, I'm not going to continue this. I'll step back one more time.

Diego, never ever reverse my commit without notice beforehand.