ivan at cacad.com
Tue Dec 30 17:30:47 CET 2003
I told you that --enable is idiotic.
I was the one that wanted to change --enable to meen autodetected
(I also proposed --force to meen force), but I was threaten that
my cvs write access will be taken away if i do such thing.
Arpi think's that the mplayer way, and Gabucino is happy if he can
confuse/abuse as many users as possible. The rest of developers
don't want to take side or doesn't care.
Or think that this is "a bug, but very small".
Anyway I got enough flames ...
Smash the bugs
Diego Biurrun said:
> On Tue, Dec 30, 2003 at 05:13:40AM +0100, Enrico Weigelt wrote:
>> hmm, would be better to have several level of automatic:
>> a) --try-enable-foo
>> ==> to autodetection. (default)
>> b) --enable-foo
>> ==> explicitly enable/disable some feature, but argue if something
>> seems to be missing/corruot
>> c) --force-enable-foo
>> ==> really enforce this feature - no matter what comes - go through
>> until the bitter end.
> Surprise, surprise, this is exactly the way it works today, under a
> different name.
> Enrico, you do not seem to have read even 5 lines of MPlayer code, nor
> run some basic tests with the MPlayer build system. This list is about
> video player development, not about next generation build systems. Sorry
> have to say this so explicitly, but you are nothing more than a troll
> Now please go away.
> MPlayer-dev-eng mailing list
> MPlayer-dev-eng at mplayerhq.hu
More information about the MPlayer-dev-eng