[FFmpeg-cvslog] r24370 - trunk/Makefile [VOTE! ;)]
Wed Jul 21 22:08:46 CEST 2010
On Wed, Jul 21, 2010 at 08:44:15PM +0100, M?ns Rullg?rd wrote:
> Michael Niedermayer <michaelni at gmx.at> writes:
> > On Wed, Jul 21, 2010 at 08:14:23PM +0100, M?ns Rullg?rd wrote:
> >> Reimar D?ffinger <Reimar.Doeffinger at gmx.de> writes:
> >> > On Wed, Jul 21, 2010 at 06:53:19PM +0100, M?ns Rullg?rd wrote:
> >> >> Michael Niedermayer <michaelni at gmx.at> writes:
> >> >> > And (redundantly) reruning configure can lead to minor changes to
> >> >> > headers that then in chain reaction cause alot more to be rebuild
> >> >> > than needed
> >> >>
> >> >> If config.h isn't changed, nothing will be needlessly rebuilt.
> >> >>
> >> >> Until you lot decide how you want it, I'm not changing anything.
> >> >
> >> > Would it be reasonable to ask y/n whether configure should be
> >> > rerun from the Makefile in this case?
> >> Interactive build systems are one of the most horrible things I know.
> >> > Might cause issues for automated systems that don't expect things
> >> > to hang forever.
> >> > How about writing "... changed, rerunning configure in 10 seconds"
> >> > and then sleep for 10 seconds?
> >> > Allows to abort and even to "touch" the right file to avoid having
> >> > to rerun configure if really desired.
> >> Ridiculous. The options are:
> >> 1. Do nothing. Old behaviour.
> >> 2. Rerun configure. Current.
> >> 3. Print warning and carry on. Easy to do.
> > 1. Print warning and carry on. Easy to do.
> > 2. Do nothing. Old behaviour.
> > 3. further discussion
> > 4. Rerun configure. Current.
> Stop it immediately or I'll do as I please ignoring any requests.
So how exactly is that going to work?
If people state their order of preferrance it qualifies as a vote
If people just state the single variant they like most its still a vote
but then one doesnt even know if one is ok with the 2nd option and just
considers it slightly worse or strongly opposes it.
And if its neither of the 2 then how should people communicate the
Stating things in a way that cannot be unambigously parsed like
I prefer that a warning is printed over old behaviour but iam ok
with the old behaviour as well. Reruning configure though does not
seem like a so good idea to me and i think this maybe should rather
be discussed first on ffmpeg-dev as reruning configure from make
really feels odd.
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
When you are offended at any man's fault, turn to yourself and study your
own failings. Then you will forget your anger. -- Epictetus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 190 bytes
Desc: Digital signature
More information about the ffmpeg-cvslog