Comment #7 on issue 14545 by m...@chromium.org: Cache dir needs to be under  
~/Library/Caches
http://code.google.com/p/chromium/issues/detail?id=14545

This might actually be a good first bug for a 20%er.

The cache directory should move so that it has the same name that we  
currently use
for the profile directory, except in ~/Library/Caches instead of  
~/Library/Application
Support.

For example, a cache directory currently in ~/Library/Application
Support/Google/Chrome/Default/Cache should move to
~/Library/Caches/Google/Chrome/Default.  A cache directory currently in
~/Library/Application Support/Chromium/Default/Cache should move to
~/Library/Caches/Chromium/Default.

Optionally, if a Cache directory is found within the profile, we can  
continue to use
that instead of the new location in ~/Library/Caches.

If the profile is outside of ~/Library/Application Support, the cache  
directory should
remain within the profile by default.  This enables profile portability.   
So does the bit
about leaving the cache in the profile if it's already found there.

This change shouldn't be terribly difficult to achieve.  The cache  
directory can be
redirected by starting at chrome::PathProvider in  
chrome/common/chrome_paths.cc
and returning the value we want for chrome::DIR_USER_CACHE.  Linux  
presently does
this.  See chrome::GetUserCacheDirectory  
chrome/common/chrome_paths_linux.cc.

(Linux is apparently not smart enough to use a different cache for each  
profile.  We
are smart enough.  We will do better.)

That said, this is on the punch list for MacBeta.  While it's a decent  
first bug for a
20%er, if a 20%er wants to take it on I'd strongly suggest starting on it  
now.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to