Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Conan migrates settings back and forth always overwriting my settings with defaults
See original GitHub issueAs suggested in documentation I’ve created my own settings.yml file which I apply using conan config install (thanks for this useful feature).
However it happens that I may have slightly different conan versions (1.2.0 and 1.2.1 in my case) depending on how I run conan (machine-wide or user-local).
Every time I run different version of conan it just wipes my setting and replaces them with default ones, which is annoying.
I see that conan has logic to not overwrite settings always, I think it just needs to be tuned, or provide an option to forbid migration completely.
Issue Analytics
- State:
- Created 5 years ago
- Comments:23 (19 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@olivren My bad 🙁 Shouldn’t reply from phone w/o access to sources thinking about something completely different…
Although there are commands for updating configuration and profiles.
Great, thanks for telling! I think this issue could be closed then. Cheers!