diff mercurial/sparse.py @ 33556:22371eabb3b1

sparse: add a requirement when a repository uses sparse (BC)

The presence of a sparse checkout can confuse legacy clients or
clients without sparse enabled for reasons that should be obvious.

This commit introduces a new repository requirement that tracks
whether sparse is enabled. The requirement is added when a sparse
config is activated and removed when the sparse config is reset.

The localrepository constructor has been taught to not open repos
with this requirement unless the sparse feature is enabled. It yields
a more actionable error message than what you would get if the
lockout were handled strictly at the requirements verification phase.
Old clients that aren't sparse aware will see the generic
"repository requires features unknown to this Mercurial" error,
however.

The new requirement has "exp" in its name to reflect the
experimental nature of sparse. There's a chance that the eventual
non-experimental feature won't change significantly and we could
have squatted on the "sparse" requirement without ill effect. If
that happens, we can teach new clients to still recognize the old
name. But I suspect we'll sneak in some BC and we'll want a new
requirement to convey new meaning.

Differential Revision: https://phab.mercurial-scm.org/D110

--- a/mercurial/sparse.py	Mon Jul 17 11:21:23 2017 -0700
+++ b/mercurial/sparse.py	Mon Jul 17 11:45:38 2017 -0700
@@ -18,6 +18,7 @@
     match as matchmod,
     merge as mergemod,
     pycompat,
+    scmutil,
     util,
 )
 
@@ -522,13 +523,14 @@
     prunetemporaryincludes(repo)
 
 def _updateconfigandrefreshwdir(repo, includes, excludes, profiles,
-                                force=False):
+                                force=False, removing=False):
     """Update the sparse config and working directory state."""
     raw = repo.vfs.tryread('sparse')
     oldincludes, oldexcludes, oldprofiles = parseconfig(repo.ui, raw)
 
     oldstatus = repo.status()
     oldmatch = matcher(repo)
+    oldrequires = set(repo.requirements)
 
     # TODO remove this try..except once the matcher integrates better
     # with dirstate. We currently have to write the updated config
@@ -538,11 +540,21 @@
     # updated. But this requires massive rework to matcher() and its
     # consumers.
 
-    writeconfig(repo, includes, excludes, profiles)
+    if 'exp-sparse' in oldrequires and removing:
+        repo.requirements.discard('exp-sparse')
+        scmutil.writerequires(repo.vfs, repo.requirements)
+    elif 'exp-sparse' not in oldrequires:
+        repo.requirements.add('exp-sparse')
+        scmutil.writerequires(repo.vfs, repo.requirements)
 
     try:
+        writeconfig(repo, includes, excludes, profiles)
         return refreshwdir(repo, oldstatus, oldmatch, force=force)
     except Exception:
+        if repo.requirements != oldrequires:
+            repo.requirements.clear()
+            repo.requirements |= oldrequires
+            scmutil.writerequires(repo.vfs, repo.requirements)
         writeconfig(repo, oldincludes, oldexcludes, oldprofiles)
         raise
 
@@ -647,7 +659,8 @@
                         len(oldexclude - newexclude))
 
         fcounts = map(len, _updateconfigandrefreshwdir(
-            repo, newinclude, newexclude, newprofiles, force=force))
+            repo, newinclude, newexclude, newprofiles, force=force,
+            removing=reset))
 
         printchanges(repo.ui, opts, profilecount, includecount,
                      excludecount, *fcounts)