[Pkg-openmpi-maintainers] [Fwd: Re: debian/patches/99autoconf]

[Manuel Prinz]

Am Dienstag, den 26.06.2007, 12:55 +0200 schrieb Sylvestre Ledru:
> Le mardi 26 juin 2007 à 05:07 -0500, Dirk Eddelbuettel a écrit :
> > Yes, and conceptually there is no reason why the same could not be achieved
> > by patching the underlying configure.ac directly.
> I am not sure that we are even touching the configure.ac ...
> If it is the case, do we have the patch for this file ?

After having a closer look at my modification, I did the 99* patch (TM)
by applying patch 10opal* with dpatch-edit-patch, ran autoreconf and
saved the differences as the 99* patch. I never touched configure.ac and
have no idea why only configure is affected since the file that was
modified is opal/asm/Makefile.am. Maybe I'm lacking of autotools skills.

By looking at 99* I get the impression that most of the changes is due
to reformatting or rewriting of functions created by autotools. The
actual difference is (just guessing!) not that big at all. I can't say
if there's anything we can do about it to shrink the patch in size.

Running autoconf during the build process would modify some files and
I'm wondering if that would break some QA tests like rebuilding the same
package twice, since debian/rules clean is expected to take back any
modifications done to the sources. Can we keep track of that when we run
autoconf at build time? That was the intension of the patch because one
can easily deapply it.

Best regards
Manuel