[PATCH evolve-ext] evolve: do not set experimental.evolution in uisetup

[Jun Wu]

On 04/03/2016 09:01 PM, Pierre-Yves David wrote:
> I don't think this will work. There is third party code (especially…
> mercurial core) that rely on the extension to set this when enabled. And I
> assume this would break it all.

Thanks. I didn't realize obsolete.py is reading it.

How about doing these instead:
- evolve.py: remove setconfig
- evolve.py: set obsolete._enabled = True

> I this time for a field test of the extensibility of chg config dispatch?

Not yet.

APIs to mark config items as sensitive are planned as we discussed in IRC,
and that will happen in extensions.py.

For chg, at present it's impossible to handle "if getconfig(x): setconfig(x)"
correctly because the information of the roriginal config value will be lost.
My ui refactoring plain will help solve the issue but that won't happen
soon.