scope of configure.optflags, configure.compiler etc. command line variables

[Ryan Schmidt]

On Sep 20, 2019, at 02:23, René J.V. Bertin wrote:

>> Storing a separate cache for each port would quickly eat up a lot of disk space.
> 
> Evidently, but
> - ccache doesn't use more space than needed
> - the ccache directory compresses extremely well with afsctool, a background cleanup process could exploit that
> - per-port caches could be removed with `port clean` (automatic if they're in the work directory) or `port clean --all` (or via a dedicated option). This would require using the -o and -k flags as long as you plan to profit from ccache benefits, but that probably covers most of the situations anyway.

It would seem that making `port clean` delete the ccache caches would defeat all current use cases of it.

Anyway, I'm going to leave the discussion now.