Re: Cache directory tagging

On Mon, 2004-08-16 at 18:57 +0200, Bryan Ford wrote:
> Hi Galeon folks,
> 
> I've been talking with the Mozilla folks and other projects for a few weeks 
> about a proposal I'm circulating, available here:
> 
> 	http://www.brynosaurus.com/cachedir/

Maybe it's just me, but it seems not all possible cases are mentioned
which makes me wonder if they were overlooked.  For example, what if the
user explicitly removes *only* the tag file?  Or edits the contents?
What should the applications do in those cases?


> The short version: I'm proposing that applications that automatically create 
> and maintain cache directories of some kind include a trivial little "tag" 
> file in the directory with a standard name and header, to provide a robust 
> and standard way to exclude those directories from backups and such.  Mozilla 
> and several other projects are already on board.  (In fact I already 
> contacted Ricardo Pascual about this a while ago, who referred me to this 
> list, but didn't have a chance to follow up until now.)

I put this in bugzilla as well:
http://bugzilla.gnome.org/show_bug.cgi?id=150277


> Implications for Galeon: Since you already inherit Mozilla's web content cache 
> code, that cache directory should be taken care of next time you update to 
> Mozilla's latest code base.  But I notice that Galeon also creates a 
> "favicons-cache" directory - assuming it's really a cache (which it appears 
> to be), would you be willing to add the 5 or 10 lines of code necessary to 
> write a tag file into this directory as well?

Seems quite unobtrusive to add, I don't see any reason why we couldn't
add that.  Maybe you could even write a reference implementation in the
spec everyone else could just copypaste?  What me lazy? ;)


-- 
Tommi Komulainen                                 [email protected]
GPG 1024D/68388EE6    6FD6 DD79 EB38 BF6F 3533  09C0 04A8 9871 6838 8EE6

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBIO6XBKiYcWg4juYRAtZLAKC7LzjmnQWufM57NguPn1lLnBQv+QCg+VSs
OZhjiQpV/StVw7B6YPJsZKI=
=6xon
-----END PGP SIGNATURE-----