conda-forge / conda-forge/yaml-cpp-feedstock
inclusion of gtest in this package
- Dominant language
- Batchfile
- Stars
- 0
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
### Comment:
It appears that this package includes `gtest` in its installation. I see that the `yaml-cpp` project does have `gtest` in its repo, but wonder if it is necessary/appropriate/best practice to include it as part of the installed package.
I raise this question because our project recently encountered a version compatibility problem when the `gtest` headers installed by `yaml-cpp` were conflicting with the version of `gtest` that we use.
I think we have an immediate solution on our end, but I'm not really sure if this packaging should be modified or not?
Contributor guide
Research direction
Review the yaml-cpp feedstock packaging and determine why gtest is included in the installed package. Compare the resulting gtest headers with the project's dependency requirements; done means deciding whether gtest should be shipped and preventing the conflicting headers if it should not be.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100