Re: [PATCH] git-svn: Destroy the cache when we fail to read it
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Aug 23, 2011, 17:05 UTC
- Message-ID
- <7vobzgrrbg.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <20110823081546.GA28091@dcvr.yhbt.net>
Eric Wong <normalperson@yhbt.net> writes:
Show 18 quoted lines
> Jason Gross <jgross@MIT.EDU> wrote:
>> my $cache_path = "$ENV{GIT_DIR}/svn/.caches/";
>
> Can we make the caches sharable by encoding variables like
> $Config{use64bitint} and $Storable::VERSION into $cache_path?
>
> Something like this (untested):
>
> use Config;
>
> my $cache_path = "$ENV{GIT_DIR}/svn/.caches/";
> $cache_path .= "$Config{use64bitint}.$Storable::VERSION/";
>
> We'll blow everybody's cache away once during the git-svn upgrade, but
> in the future people will be able to share the same working tree between
> different versions of perl/Storable/whatnot without needing extra code
> to detect croaks, different build options, and nuking each other's
> caches.Meaning multiple directories and people share with those with systems with similar characteristics? It certainly is better than silently getting confused or barfing when reading 32LE data on 64BE box, and presumably it would be easy to implement, but is that the best we can do with memoize?
I am wondering if memoize can be told to use a platform independent serializer backend that is reasonably efficient.