Many thanks for the answer!
On 5 November 2012 14:53, Andrew Stubbs a...@codesourcery.com wrote:
My first reaction to this issue, rightly or wrongly, is that it's more of
a documentation issue than a real bug. I mean, it can only occur if two
people share a cache, or if the user installs new
On 5 November 2012 16:31, Andrew Stubbs a...@codesourcery.com wrote:
Incidentally, you appear to have committed a patch updating the
documentation stating that direct mode is off by default, but in the code
direct_mode is still true, by default.
Yes, I started sketching on disabling it by
On 7 November 2012 14:19, Joel Rosdahl j...@rosdahl.net wrote:
Hm. Coming to think of it, nothing stops Fedora et al from disabling direct
mode by default even if ccache's own default is to enable it.
As a package maintainer I would like to discourage this view.
Downstream maintainers shouldn't
On 04/11/12 19:10, Joel Rosdahl wrote:
The direct mode, which was introduced in version 3.0 almost three years
ago, has a design bug. The essence of the problem is that in the direct
mode, ccache records header files that were used by the compiler, but it
doesn't record header files that were
On 04/11/12 19:10, Joel Rosdahl wrote:
Since a quick fix likely isn't possible in the short term, and I would like
to release ccache 3.2 soon, we have to decide whether the direct mode
should default to off or on. Please share any opinions!
Incidentally, you appear to have committed a patch
