Make cmake-scripts a conan package instead of a git submodule?

[MBetters]

Thanks for the project template. I'm putting it to good use.

I have a workspace with multiple submodules. I'd like to convert all those submodules to use this template. However, this would cause the cmake/common --> cmake-scripts submodule to be duplicated multiple times, which is messy. I could use a tool like https://github.com/chronoxor/gil to avoid the submodule duplication, but would rather not introduce another tool to my workflow.

Do you think it'd be worthwhile to turn the cmake/common --> cmake-scripts submodule into a conan package? That way, any project that uses cmake-scripts could just add it to the conanfile.py's depends = "...".

I'm curious if you think there's a better approach for a multi-submodule workspace, where each of the submodules is based on this project template? If you think turning cmake-scripts into a conan package is worthwhile, I'll make the changes myself and add it as PRs to both repos.

[mpusz]

Sorry, for not answering for so long. I didn't notice when you created this issue.

Yeah, I thought about adding it as a Conan package but it will:

1. Force everyone to use Conan
2. Require me to put conan_init in every repository rather than in one place which is not too convenient :-(