Bug 1258744 - Installing ccache should not force its wrappers into PATH
Installing ccache should not force its wrappers into PATH
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: ccache (Show other bugs)
22
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ville Skyttä
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-01 03:42 EDT by Tor Lillqvist
Modified: 2015-11-19 13:55 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-09-01 10:51:08 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tor Lillqvist 2015-09-01 03:42:08 EDT
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.
Comment 1 Ville Skyttä 2015-09-01 10:51:08 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.