On Wednesday, February 3, 2016, Eric A. Borisch <ebori...@macports.org> wrote:
> On Monday, February 1, 2016, Daniel J. Luke <dl...@geeklair.net > <javascript:_e(%7B%7D,'cvml','dl...@geeklair.net');>> wrote: > >> On Feb 1, 2016, at 3:09 PM, René J.V. Bertin <rjvber...@gmail.com> wrote: >> > As an example of a potentially non-trivial file for automatic checksum >> updating >> >> I don't think this would be as hard to implement as you seem to think it >> would be. >> >> 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). >> > > 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 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.) > https://trac.macports.org/changeset/145398
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
