On Wednesday, February 3, 2016, Eric A. Borisch <<a href="mailto:eborisch@macports.org">eborisch@macports.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Monday, February 1, 2016, Daniel J. Luke <<a href="javascript:_e(%7B%7D,'cvml','dluke@geeklair.net');" target="_blank">dluke@geeklair.net</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Feb 1, 2016, at 3:09 PM, René J.V. Bertin <<a>rjvbertin@gmail.com</a>> wrote:<br>
> As an example of a potentially non-trivial file for automatic checksum updating<br>
<br>
I don't think this would be as hard to implement as you seem to think it would be.<br>
<br>
As a first try, a really simple s/$oldchecksum/$newchecksum/ would probably work (I'm perhaps not creative enough to think of a use-case where that would false-positive and change something unintended).<br>
</blockquote><div><br></div><div>I will try to check in a tool I've used to automate this later tonight; I just need to find a few moments to put the macports license boilerplate in it first. It is a python script that drives the port command to determine what (if any) checksums need to be updated for a port, and then uses sed to actually (s/old/new/) update<span></span> it. It runs sed with no backup, so it is best used in an svn version so you can see what it has changed. (Or it could be modified to create a backup file easily enough.)</div></blockquote><div><br></div><div><span></span> <a href="https://trac.macports.org/changeset/145398">https://trac.macports.org/changeset/145398</a></div>