Hi Heiner, On 10/6/06, Jens-Heiner Rechtien <[EMAIL PROTECTED]> wrote:
maybe here are a few words in order to explain how release engineering handles 'configure'. If there are two CWSs with conflicting changes to 'configure' integrated at the same time - and they will conflict if there are two versions of configure.in or just two different versions of autoconf - RE will regenerate 'configure' and commit it. We use a pretty old versions of autconf, I think it 2.59. We like it to always use the same version of autoconf, because this keeps the diffs small and we are least able to quick check of the plausibility of configure. Always using the same version of autoconf is therefore not an absolut must but a convenience. If 2.59 is no longer good enough please tell us which version of autoconf is the agreed on best version nowadays.
Thanks for the clarification. The version of autoconf on OpenSUSE 10.1 seems to be 2.59, so I guess it's acceptable.
PS: A developer needs not to check in 'configure', there is a standing agreement that RE will regenerate it during integration. It has happened that we overlooked it so it never hurts if you commit it, too. A conflict will not be overlooked by us :-)
Well, too late. I've already commited it, so.... ;-) Kohei --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
