port reclaim: allow disabling ccache cleanup by default, via cmd-line options and/or config

[mascguy (Christopher Nielsen)]

While the new ccache cleanup functionality in 2.7.x is great, users should have the ability to configure whether it runs by default. And that configuration setting should affect both the default answer for interactive reclaim mode, as well as whether it's enabled during non-interactive runs (via `port -N reclaim).

This is particularly important for MacPorts developers, as we generally prefer to NOT wipe the ccache area during reclaim. And it's a royal pain to have to run via interactive mode each time.

[jmroot (Joshua Root)]

It seems like reclaim is a potentially destructive operation in non-interactive mode in general, in the sense that it could easily remove more than you want. It at least has dry-run support, but config options and actionflags for turning all of its functions on and off may be a good idea.

[mascguy (Christopher Nielsen)]

Great point Josh. The implementer should consider including cmd-line action flags, in addition to supporting configuration options.

[mascguy (Christopher Nielsen)]

Haven't had a chance to look at this yet, but hoping to get to it over the next few weeks.

[mascguy (Christopher Nielsen)]

Reflecting on this over the past month or two, this isn't a big deal: Most of the functionality of port reclaim can be accomplished by port -f uninstall inactive, followed by port clean --all installed. (Though folks who retain inactive ports as part of their workflow, wouldn't want to forcibly uninstall those.)

Then there's the option to use the various pseudo-portnames, like leaves and rleaves, to identify things not necessary.

It's still worth implementing though. But given that there are plenty of alternative means available, this isn't necessarily a high-priority.

However, we'll get to it eventually.