[question] Managing MSYS build require outside of the recipes

Coming from https://github.com/conan-io/conan-center-index/pull/971#discussion_r384523076

To enable proper MinGW support in some of the recipes, we are repeating every time the code

def build_requirements(self):
    if tools.os_info.is_windows and "CONAN_BASH_PATH" not in os.environ and \
        tools.os_info.detect_windows_subsystem() != "msys2":
            self.build_requires("msys2/20190524")

I personally understand that it is very convenient to have the build require there, but this is clearly a pattern in all the recipes that enable support for MinGW.

My question is: Should we stop adding this code in the recipes and recommend people using the msys package in their mingw profiles as the cannonical way to create the packages?

I think having msys together with mingw should be a well-known pratice for all of those that are these creating packages

cc/ @SSE4 @uilianries @madebr

[madebr]

No, the build requirement must be there.

It is often present for MSVC builds if there is only a autotools build system.

[danimtb]

Thanks a lot for the feedback guys!