Red Hat Bugzilla – Bug 1258744
Installing ccache should not force its wrappers into PATH
Last modified: 2015-11-19 13:55:11 EST
Description of problem:
Installing ccache forces it to be used by prefixing PATH with /usr/lib64/ccache (through /etc/profile.d/ccache.sh) that contains the wrappers for gcc, clang, etc.
Sure, that could be seen as a feature, but in some cases it is unhelpful. IMHO even if ccache is installed, actually using it should be opt-in by explicit developer action in each build tree for software they are building.
It's not being forced: the whole /etc/profile.d/ccache.*sh scripts are config files where the local admin can change the default behavior, users can modify their $PATHs, and as documented in the ccache man pages and the profile.d scripts, CCACHE_DISABLE can be used to opt out.
I disagree quite strongly with opt-in being better default behavior than the current opt-out, and it's going to take more than an "IMHO" to convince me otherwise :) If you care deeply about this, I suggest discussing it for example on the devel list, and if the clear conclusion and consensus is that this stuff should be opt-in (in addition to the opt-in already made by someone by installing the package and leaving the defaults as they are), then there is a case why things should change.