On Mar 26, 2018, at 00:18, Sean Farley wrote: >>> -checksums rmd160 daf92f73deaabf529c3bfa883fbd178b33ca4825 \ >>> - sha256 >>> df907126ca75bb7ade45015e681269718b1f1dad7eb2e605fd40efebb8e4fdd3 >>> +checksums rmd160 b129990e2a4f2f56dd15b2562b8668ca5a3d615c \ >>> + sha256 >>> 1e7d20d20eb26da307d36017461fe4a55f40e947e232739179dbe6412e22ed13 >> >> Please add size to checksums at your convenience as you update ports. > > Ah, ok. Did something change recently?
The possibility to add the size to the checksums was added in MacPorts 2.3.0; I missed it at the time. Rainer added the size to the checksums of port a few months ago, which alerted me to its existence. The size is verified along with the checksums of course. A future version of MacPorts may do more with this information, such as an aggregate file download progress bar if multiple ports are fetched, so we would like all ports to eventually provide this metadata. > If so, should we output the > desired checksum values in 'port -v fetch FOO'? That's how I usually > update the checksum values. Or maybe there is another way I missed? I already made this change in master. We have not released a new version of MacPorts since then.
