Consider not using the CACHE in conan install

There is the issue https://github.com/conan-io/conan/issues/1015, which is creating problems due to the caching. But not only because of this.

It is true, that caching of settings/options/env is necessary for build, source, package, etc conan commands. But maybe conan install should always make explicit the inputs, via command line. “Explicit is better than implicit”. Same for conan test_package.

Even if this can break something, it is extremely easy to fix, just provide a profile or settings in the command line, i.e. nothing to fix inside conan, just in the conan command invocation by users.

What do you think?

[tru]

Yeah I am for this. This was really hard to find and debug when I ran into it the other day.

[sztomi]

Me too, I regularly test a package with different settings and I often run into a situation where I just end up deleting the whole package directory.

But maybe conan install should always make explicit the inputs, via command line

I’d say it should work with defaults, but if the settings are provided, conan should use those. Is this what you mean by this?