Talk:Ccache

Mainly for developers?
Regarding this commit, why is ccache mainly for developers all of the sudden? Ni1s 08:44, 18 September 2009 (GMT)
 * Hi, Ni1s. Look at this blog post by Diego E. “Flameeyes” Pettenò. Although I don't know much about compilers, it seems quite apparent for me. Anyway, if you're sure I'm wrong, can you fix it? Thanks. - Lolo 07:06, 19 September 2009 (GMT)
 * In some ways this makes sense I guess and the article by Diego explains most of that reasoning. Developers I imagine, based on my own experiences, end up testing out an ebuild several times with various changes and/or circumstances before committing new ebuilds and/or fixes. To this extent, compiling with ccache speeds up that process slightly. What isn't explained is if your compiler changes (ie. GCC 4.3.3 -> 4.4.x, not a whole new compiler). Will ccache still be useful? I would assume no, but I don't know enough about how ccache works myself to say that for sure. Anyways, I think changing the text "mainly for developers" to something like "mostly beneficial to developers" would be more appropriate wording. Just my opinion though. Mousee 08:56, 19 September 2009 (GMT)
 * Why bother with the wording at all? What ever reason one might have for using ccache, either as a user or a developer, is entirety up to themselves. The intro could of course benefit from being more precise on where ccache might be useful. /Ni1s 16:47, 21 September 2009 (GMT)

Actually, its useful for users when they release those -r1 -r2 revisions of the same ebuild with options you might not be using - 192.117.134.22 01:04, 14 October 2009 (GMT)