On Wed, 3 Mar 2010 05:00:48 -0500
Mike Frysinger vapier@gmail.com wrote:
make the default a ./configure option that defaults to off
I would prefer not to make a build-time option of this, because then the
documentation has say something in line with whether files are compressed by
default
On Thu, Mar 4, 2010 at 16:00, Joel Rosdahl wrote:
On Wed, 3 Mar 2010 05:00:48 -0500 Mike Frysinger wrote:
make the default a ./configure option that defaults to off
I would prefer not to make a build-time option of this, because then the
documentation has say something in line with whether
On Wed, 3 Mar 2010 10:39:47 +
Dalton, Tom tdal...@hp.com wrote:
I would say for the first release of a new feature, default it to off. That
gives people a chance to 'play' with it without potentially breaking existing
installations that are simply upgrading. If there are no major problems
4 mar 2010 kl. 22.30 skrev Joel Rosdahl:
On Wed, 3 Mar 2010 10:39:47 +
Dalton, Tom tdal...@hp.com wrote:
I would say for the first release of a new feature, default it to off. That
gives people a chance to 'play' with it without potentially breaking existing
installations that are
On Tue, Mar 2, 2010 at 17:10, Joel Rosdahl wrote:
Lars Gustäbel's compression patch (which will be incorporated in ccache 3.0)
enables compression by default, and if you don't want compression you have to
set CCACHE_NOCOMPRESS. I'm still a bit undecided about whether defaulting to
compression
I would say for the first release of a new feature, default it to off. That
gives people a chance to 'play' with it without potentially breaking existing
installations that are simply upgrading. If there are no major problems with
the feature in that first release then make it a default in the
