about keeping a checksums table in a separate file

Daniel J. Luke dluke at geeklair.net
Mon Feb 1 10:16:03 PST 2016

Maybe, instead of having your portfile reference an external file (with contents generated from port -v checksum), we should add a `port checksum` option that updates the Portfile with the (new) checksums?

> On Jan 31, 2016, at 2:28 PM, René J.V. Bertin <rjvbertin at gmail.com> wrote:
> On Sunday January 31 2016 18:53:32 Rainer Müller wrote:
>> Personally, if a upstream checksum is available, I insert it into the
>> Portfile while updating the version number. Then I can generate the
>> others using 'sudo port -v checksum' and insert them into the Portfile.
> That's comparable to what I used to do, with a foreach loop over all subports doing port -v checksum in the shell, redirected to a file. That leads to a lot of copy/pasting though, and I've been known to make errors in the process.
> The other thing that has bitten me quite a few times is that using the port command for this can wipe your build directory (which may not yet be desirable when you're just updating the checksums), and more or less obliges you to add the variants you're going to use later on. 

Daniel J. Luke

More information about the macports-dev mailing list