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

[Dirk Eddelbuettel]

Hi Manuel,

Nice to hear from you, but very sorry about the circumstances. Are you ok?

On 25 June 2007 at 22:01, Manuel Prinz wrote:
| Am Sonntag, den 24.06.2007, 10:09 -0500 schrieb Dirk Eddelbuettel:
| > As you and both don't seem to know, why don't we stop conjecturing and wait
| > for Manuel to sort this out, ok ;-) ?
| 
| Sorry for causing confusion! One of the patches [1] modified one or more
| of the Makefile.am files. So all I did was applying all patches, run
| "autoreconf" to apply the changes in the Makefiles and running dpatch,
| saving the changes as 99*.
| 
| At least that was what I thought Steve did: He modified some autotools
| input files, saved the patch as a single patch and saved the
| modfications done by invoking autoreconf as 99* dpatch. So one doesn't
| really need to care about the modifications done in the autogenerated
| files, having the "real" changes in a seperate patch.
| 
| Maybe I heavily misunderstood this technique. I guess running automake
| as part of the build process after applying the patches might work, but
| you won't get back to pristine sources afterwards because those can't be
| deapplied again. Or did I get something wrong here?

That's a fair point. We surely want it to be reversible. 

But let me just try to think out loud here:

1)  debian/patches/99* modifies some .am/.ac files
2)  before calling configuire, we call autoconf/automake as needed

3)  we build as usual thanks to 1) and 2)

4)  clean removes the generated configure script
5)  dpatch unapplies the diffs from 1) and we're fine

Now, all of that is of course hypothetical unless we get the set of changes
to the .ac/.am files back. Do you still have them?  

Cheers, Dirk

-- 
Hell, there are no rules here - we're trying to accomplish something. 
                                                  -- Thomas A. Edison