Use size from checksums for curl progress bar when server does not supply length header

[ryandesign (Ryan Carsten Schmidt)]

When MacPorts is fetching a distfile using libcurl, and the web server does not supply a Length header, MacPorts does not know how big the file is, so it can't display a determinate progress bar and has to fall back on an indeterminate progress bar. GitHub's automatically generated tarballs are a common example of when this happens.

MacPorts now has support for portfile authors to indicate the filesize in the checksums line, using the checksum type size.

For distfiles that indicate their size in this way, MacPorts should be able to use that information to display a determinate progress bar, even if the server doesn't supply the length.

[raimue (Rainer Müller)]

This is reasonable, but it is not as easy as I originally thought. At the moment, we just rely on the progress function of curl, so we would need to pass the expected size to the curl Tcl command and then pass it through to the progress function to calculate the expected time. Also the checksums option is only parsed in the checksums phase, so that would neeed to be moved to be done earlier.

[jmroot (Joshua Root)]

Ticket retargeted after milestone closed