On 11.01.2011 16:01, Julian Foad wrote: >> I see a different issue here: The close_wcroot() call is normally >> handled from pool cleanup for users of the svn_client api. (The >> svn_wc_context_t is cached in the client context, which is only closed >> on pool cleanup). > Thanks for pointing that out. That is not when I would like the > pristine cleanup to happen. I would like it to happen after every > operation that changes the WC - say after every major call into > libsvn_wc, and/or every major call into libsvn_client, or whenever the > wc.db work queue is run. Any thoughts on where would be best?
What exactly are you trying to achieve? Is this a disk-space optimization? My hunch says that you do not want to do this too often at all because it'll turn out to be space-vs-time. Deleting a file isn't cheap even on a local filesystem these days. Better to relegate this to an explicit "svn cleanup"; or better yet, follow CMike's advice. -- Brane
