> On Aug 10, 2016, at 9:04 PM, Ryan Schmidt <[email protected]> wrote: > >> On Aug 10, 2016, at 5:15 PM, Mojca Miklavec <[email protected]> wrote: >> >> The major problem is that there is basically no way to predict how >> much space an installation of a port from source might need (one might >> be able to do some heuristics based on old build logs from the >> buildbot or so, but that might be quite some work for very little gain >> and it won't work well for non-default variants etc). > > It would be easy for the buildbot to record the size of the installed > package, even if the package isn't distributable, and could submit that > information to our hypothetical new web site, from which MacPorts could query > it.
This could be helpful, but it wouldn't provide information about the *maximum* disk space required by a build, which could easily surpass the size of the final build products. vq _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
