Hi, I've been thinking about using distcc in my laptop to have my PC helping emerging packages, but I realized that to disable it I have to write to make.conf and remove features, save it and emerge things, and later, revert changes. I want to say, when I am out of my home, I don't want to use distcc for obvious reasons, so I suggest having distcc *always* configured and an external option to safely disable it. I know it can be done with FEATURES="-distcc" but it is not suggested to do ACCEPT_KEYWORDS="~arch" so I though it is not also suggested to use FEATURES="-distcc" and have instead an option to handle it internally. What do you think about this issue? Reproducible: Always
I seems to me that portage should really be unaware of toolchain internals like ccache and distcc. Ideally it would be handled by some other layer, like gcc-config.
FEATURES=-distcc sounds just peachy compared to any other option alias nodistcc='FEATURES=-distcc emerge'
Why do you need an emerge option for this? Using ACCEPT_KEYWORDS="~arch" is generally not recommended because it will immediate downgrade after you've emerged something like this, completely irrelevant with things like FEATURES="distcc" (In reply to comment #1) There's Bug 128810 for this, and I personally hate the suggestion. It's just fine as it is.
As Zac said, portage shouldn't really care about toolchain stuff (unfortunately we have to to some degree, but we shouldn't extend this unless absolutely necessary).
