about keeping a checksums table in a separate file

Eric A. Borisch eborisch at macports.org
Wed Feb 3 22:33:24 PST 2016

On Wednesday, February 3, 2016, Eric A. Borisch <eborisch at macports.org>

> On Monday, February 1, 2016, Daniel J. Luke <dluke at geeklair.net
> <javascript:_e(%7B%7D,'cvml','dluke at geeklair.net');>> wrote:
>> On Feb 1, 2016, at 3:09 PM, René J.V. Bertin <rjvbertin at 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.)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20160204/b5655f89/attachment.html>

More information about the macports-dev mailing list