version 2.1 release

diff --git a/ccache.1 b/ccache.1
index 8bada69e15fb6a6b5e0c23c21b3b7d53f2b820bf..24242391ae4c54055bec2ff679ef24980ec33576 100644 (file)
--- a/ccache.1
+++ b/ccache.1
@@ -248,6 +248,33 @@ compiler output that you would get without the cache\&. If you ever
 discover a case where ccache changes the output of your compiler then
 please let me know\&.
 .PP 
+.SH "SHARING A CACHE" 
+.PP 
+A group of developers can increase the cache hit rate by sharing a
+cache directory\&.  The hard links however cause unwanted side effects,
+as all links to a cached file share the file\&'s modification timestamp\&.
+This results in false dependencies to be triggered by timestamp-based
+build systems whenever another user links to an existing
+file\&. Typically, users will see that their libraries and binaries are
+relinked without reason\&.  To share a cache without side effects, the
+following conditions need to be met:
+.PP 
+.IP o 
+Use the same \fBCCACHE_DIR\fP environment variable setting
+.IP o 
+Set the \fBCCACHE_NOLINK\fP environment variable
+.IP o 
+Make sure that all users have write permission in the entire
+cache directory (and that you trust all users of the shared cache)\&. 
+.IP o 
+Tell your users to set a umask that allows group writes
+(eg\&. umask 002)
+.IP o 
+Make sure that the setgid bit is set on all directories in the
+cache\&. This tells the filesystem to inherit group ownership for new
+directories\&. The command "chmod g+s `find $CCACHE_DIR -type d`" might
+be useful for this\&.
+.PP 
 .SH "HISTORY" 
 .PP 
 ccache was inspired by the compilercache shell script script written

diff --git a/web/ccache-man.html b/web/ccache-man.html
index c80dea509867ee3176efc476d0928a0d1d32a40c..3c606f1378ad6767e037278a5cc739d9c40950bb 100644 (file)
--- a/web/ccache-man.html
+++ b/web/ccache-man.html
@@ -198,6 +198,28 @@ all warnings etc) from the cache.
 compiler output that you would get without the cache. If you ever
 discover a case where ccache changes the output of your compiler then
 please let me know.
+<p><h2>SHARING A CACHE</h2>
+    
+<p>A group of developers can increase the cache hit rate by sharing a
+cache directory.  The hard links however cause unwanted side effects,
+as all links to a cached file share the file's modification timestamp.
+This results in false dependencies to be triggered by timestamp-based
+build systems whenever another user links to an existing
+file. Typically, users will see that their libraries and binaries are
+relinked without reason.  To share a cache without side effects, the
+following conditions need to be met:
+<p><ul>
+  <li > Use the same <strong>CCACHE_DIR</strong> environment variable setting
+  <li > Set the <strong>CCACHE_NOLINK</strong> environment variable
+  <li > Make sure that all users have write permission in the entire
+  cache directory (and that you trust all users of the shared cache). 
+  <li > Tell your users to set a umask that allows group writes
+  (eg. umask 002)
+  <li > Make sure that the setgid bit is set on all directories in the
+  cache. This tells the filesystem to inherit group ownership for new
+  directories. The command "chmod g+s `find $CCACHE_DIR -type d`" might
+  be useful for this.
+</ul>
 <p><h2>HISTORY</h2>
     
 <p>ccache was inspired by the compilercache shell script script written

diff --git a/web/index.html b/web/index.html
index 6c76ee22eb19d2499bdd82e061ca842cd6b7bf34..f36299d759a42697d54ffcb8ec7ae07e41dd7e00 100644 (file)
--- a/web/index.html
+++ b/web/index.html
@@ -18,7 +18,9 @@ in C with more features and better performance.<p>
 
 <h2>Latest release</h2>
 
-The latest release is ccache 2.0. This release adds:
+The latest release is ccache 2.1. This release fixes a segv introduced
+for a a simple compile with 2.0. The 2.0 release had the following
+features:
 
 <ul>
 <li>minor Makefile install fixes