Re: [ccache] PATCH: Look at include files' mtimes

2012-05-28 Thread Wilson Snyder

 I can't say I'm particularly interested in supporting two manifest
 versions simultaneously

I agree that supporting only the latest should be enough.

Coming to think of it, perhaps it would be a good idea to include the
manifest version in the manifest hash so that ccache versions using
different manifest versions won't even try to read each others'
manifest files? (Currently, ccache overwrites incompatible manifest
files with its own version.)

Allowing multiple versions to co-reside and not trash each
other's result would be useful.  Presently I need redefine
CCACHE_DIR for each version to avoid overlap, which is
annoying.  (On a large multi-os cluster it often isn't possible
to roll out a new version simultaneously.)

Although... if the stats format changes overlap must still
be avoided.  Including the version number in the stats
filename would solve that too.
___
ccache mailing list
ccache@lists.samba.org
https://lists.samba.org/mailman/listinfo/ccache


Re: [ccache] PATCH: Look at include files' mtimes

2012-05-28 Thread Wilson Snyder

 Allowing multiple versions to co-reside and not trash each
 other's result would be useful. =A0Presently I need redefine
 CCACHE_DIR for each version to avoid overlap, which is
 annoying. [...]

 From the top of my head, the issues I'm aware of regarding different
ccache versions accessing the same cache directory are:

* 3.1 throws away statistics counters from future ccache versions,
which is annoying but shouldn't be critical.
* 3.1 and =3.1 have different methods of locking and updating the
stats files. If you're unlucky, the stats files (including the cache
size limits) could be garbled.

Do you know of more issues than the above?

I don't know of specific recent issues.
___
ccache mailing list
ccache@lists.samba.org
https://lists.samba.org/mailman/listinfo/ccache