Conan: Scopes

[lasote]

• Conan test command should offer scopes
• Would be great if you can self.output.warn(self.scope)
• conan install command caches "conaninfo.txt" file with the scopes variables, but you cannot remove the scopes vars unless you delete the conaninfo.txt. I suggest to do:

conan install --scope !somevar

• Would be great if you have a special pattern to specify "all the packages in the tree" so the scope is applied to all dependencies:

conan install --scope ALL:somevar

[memsharded]

I am changing, to a more general (and I think intuitive scope).
The syntax for user will be:

$ conan install --scope MyScope=True
$ conan install --scope MyScope=False # to negate, instead of weird !MyScope

Furthermore, arbitrary values are also allowed for scopes, not only True or False. Is this OK?

[memsharded]

For the ALL approach, I have tried some pattern approach, but too complicated, both implementation and usage, and handling corner cases. I have just implemented the ALL to refer to all dependencies. Note, it will be additive and specific scopes have precedence over the ALL, that is ALL:myscope=True, Hello:myscope=False => Hello:myscope will be False

[memsharded]

Question for the OUTPUT issue with self.output.info(self.scope).
I have implemented the output as dev=True, other=False. OK?

[lasote]

All in 0.10.0