# Should we have a dedicated repo for infrastructure?

**URL:** <https://discourse.bemanproject.org/t/should-we-have-a-dedicated-repo-for-infrastructure/226>\
**Category:** Beman Project Development\
**Created:** [September 30, 2024, 5:23pm UTC](https://discourse.bemanproject.org/t/should-we-have-a-dedicated-repo-for-infrastructure/226 "2024-09-30T17:23:12Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![bretbrownjr](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.bemanproject.org/bretbrownjr/32/43_2.png) [@bretbrownjr](https://discourse.bemanproject.org/u/bretbrownjr)\
**Post date:** [October 1, 2024, 12:17pm UTC](https://discourse.bemanproject.org/t/should-we-have-a-dedicated-repo-for-infrastructure/226/3 "2024-10-01T12:17:47Z")

</div>

Additional needs:

- Reducing CMake boilerplate
- Making it easier to support library layout expectations on different environments
- Making GitHub Actions less repetitive by having common build-run-and-test scripts, etc.

I have had in mind adding dependencies to account for the above also. But I have been hesitant to do so before we get some reasonable support for Conan and vcpkg.

It would be possible to use FetchContent for this, I believe. Perhaps that is the best option for now. But we should be willing to prioritize support of packaging, even if we have to rethink our use of git-submodules, for instance.

---

_[View the full topic](https://discourse.bemanproject.org/t/should-we-have-a-dedicated-repo-for-infrastructure/226)._