[SVN-749] libsvn_wc loggy operations should be revamped

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: all
• Fix Version/s: 1.7.0
• Component/s: libsvn_wc
• Labels: needsdesign
• Assignee: Unassigned
• Reporter: Greg Stein
• Created: 18/Jun/02 18:16
• Updated: 27/Oct/18 16:28
• Resolved: 02/Feb/11 20:22

Description

The WC operations that alter stuff in .svn should be isolated at the
code level. It isn't enough to have a human-level policy on what needs
to be loggy and what cannot. At some point, a human will miss the
policy and create a bug that leaves the WC admin area in an
inconsistent state.

Specifically, we should have a "open admin area" function that locks
the directory, and returns a baton. That baton is then needed to
perform modifications, or even to (say) return a pathname to a
text-base (preventing a person from modifying the text-base without
the lock and its baton). Note that we can also read and cache the
entries in the baton, then write them out when the baton is closed
(and the log is run and the lock removed), thus optimizing the whole
multiple read/write of the entries that we're doing now.

Issue Links

• blocks: SVN-703 Successful commit + failed post-commit = badness?
• depends upon: SVN-3357 Working Copy - Next Generation Library
• is blocked by: SVN-3357 Working Copy - Next Generation Library
• is depended upon by: SVN-703 Successful commit + failed post-commit = badness?
• is duplicated by: SVN-796 svn_wc_process_committed incompatible with access-baton system
• is duplicated by: SVN-628 make update-editor more crashproof