This is an archive of the discontinued Mercurial Phabricator instance.

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

Authored by indygreg on Jul 17 2017, 3:15 PM.

Details

Summary

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.

Diff Detail

Repository
rHG Mercurial
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

indygreg created this revision.Jul 17 2017, 3:15 PM
martinvonz added inline comments.
mercurial/sparse.py
526

It feels like this would be clearer as two method: the old one and a new one that just turns sparse off. That would ideally unlink .hg/sparse, no? The new method would not accept includes, excludes, or profiles, and force also doesn't seem relevant as far as I can tell.

durin42 accepted this revision.Jul 17 2017, 5:49 PM
This revision is now accepted and ready to land.Jul 17 2017, 5:49 PM
indygreg added inline comments.Jul 17 2017, 6:26 PM
mercurial/sparse.py
526

Yes, it would be cleaner to have a dedicated function to turn off sparse. Yes, it would unlink .hg/sparse. I was being a bit lazy when I wrote this patch because I wanted to get something in before the freeze :)

martinvonz added inline comments.Jul 17 2017, 7:03 PM
mercurial/sparse.py
526

I've accepted this version, but please send a follow-up (probably after the freeze), because this got pretty hard to read (relative to what it could be).

This revision was automatically updated to reflect the committed changes.