Feature Request: conan_add_remote() should not overwrite existing remote

[fschoenm]

trafficstars

We could use a feature where conan_add_remote() in CMake adds a default location for a remote if it does not yet exist. However, when the remote already exists (and possibly points to a different location than the default) it should not be overwritten.

What do you think about this idea or is there a different way to achieve this?

[czoido]

Hi @fschoenm, Could you please tell me a little bit more about the use case? I personally think that maybe it would be a better idea to have this information outside the CMake file using something like conan_config_install and install from a common location or just pre-configuring the environment with conan directly.

[fschoenm]

My use case is that our internal conan server can be reached by two different hostnames and ports, depending on which network you're in (locally or VPN). However, I wanted to make it as easy as possible to setup a development environment, which is why I used conan_add_remote() to add an initial remote to the conan environment.

I don't know conan_config_install yet. Maybe that's a better way to do the initial setup.