2014-05-14 12:33, Richardson, Bruce: > > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > > > > You would like to have a synchronization of your generated .config file > > with the configuration template. But it's not possible for the simple > > reason that you may have modified your .config file so there is no simple > > correlation with the original template. > > Would you agree then that the ideal state matrix for a make install should > probably be: * template unmodified, config unmodified - No issue - > regenerate or not as best suits the code * template unmodified, config > modified - don't regenerate, keep local config * template modified, config > modified - flag an error, since continuing compile with old config on new > code will lead to undefined build results, since config template changes > rarely occur without code changes to go with them. * template modified, > config unmodified - regenerate new config, overwriting old one, for the > same reason above. [Optionally print out message stating that the config is > being regenerated] > > Does this seem reasonable to you? The last case is the common case for me in > development, as I've had multiple build errors and unexpected build results > in the last week alone due to config template changes not propagating as I > switch development branches to work on different features.
It seems reasonable. So you plan to send a v2 with this algorithm? -- Thomas
