Hello Robert,<br><br><div class="gmail_quote">On Wed, Jan 27, 2010 at 7:21 PM, Robert Ancell <span dir="ltr"><<a href="mailto:robert.ancell@gmail.com">robert.ancell@gmail.com</a>></span> wrote:<br><div><snip> <br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> - Patches that modify <a href="http://configure.ac" target="_blank">configure.ac</a> or Makefile.am(s) - we then need a<br> second patch to update configure and Makefile(s). Ideally we'd like<br> to regenerate these before each package build but autotools version<br> mismatches tend to stop this from working reliably. I don't know if<br> there is a good solution for autotools though.<br></blockquote><div><br>A lot of developers do regenerate these files reliably by running ./autogen.sh or autoreconf or CDBS autotools magic in debian/rules. I personally think its silly to patch a file like <a href="http://configure.ac">configure.ac</a> or Makefile.am if you're not going to regenerate the autotool files as it effectively makes your patch to those files pointless. Its also painful to patch the autogenerated autotool files themselves as you need to refresh the patches every time those files get regenerated making it more painful if you want to do a quick build of say simple-scan from trunk. ;)<br> <br>Cheers,<br></div></div><br>-- <br>Cody A.W. Somerville<br>Software Systems Release Engineer<br>Foundations Team<br>Custom Engineering Solutions Group<br>Canonical OEM Services<br>Phone: +1-781-850-2087<br>Cell: +1-613-401-5141<br> Email: <a href="mailto:cody.somerville@canonical.com">cody.somerville@canonical.com</a><br>