<br><br><div class="gmail_quote">On Feb 6, 2008 10:33 PM, <<a href="mailto:skip@pobox.com">skip@pobox.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br> Michael> I need to change the way configure works for a port. Is it<br> Michael> better to patch configure or change the underlying files and<br> Michael> regenerate configure?<br><br>Patching configure is going to be very fragile. Your patch will almost<br>
certainly break with the upstream authors upgrade to a newer version of<br>autoconf. If you absolutely, positively have to patch something, patch the<br>inputs to configure, not configure itself.<br></blockquote></div><br>
<div><span class="Apple-style-span" style="color: rgb(136, 136, 136);"><div><br class="webkit-block-placeholder"></div><div>This sounds like a better plan. How do I get macports to regenerate the files once I patch the configure inputs?</div>
<div><br class="webkit-block-placeholder"></div><div>On a related note. Is there any good examples of replacing AC_CHECK_HEADERS macros with pkg-config?</div><div><br class="webkit-block-placeholder"></div></span></div>