SSE4

> I would like to see that the CCI bot is outputting all hook warnings as a comment in the PR, but not blocking the PR because of it yes,...

> @SSE4 do you think you can write black on white the proposal and add a PR to this branch here: https://github.com/jgsogo/conan-center-index/tree/policy/patching-update Let's see if we can finish that piece...

@jgsogo check https://github.com/jgsogo/conan-center-index/pull/5

@uilianries conflicts, please rebase

potential list of patterns to be scanned in hook: - `.names["cmake_find_package"]` - `.names["cmake_find_package_multi"]` - `.filenames["cmake_find_package"]` - `.filenames["cmake_find_package_multi"]` - `set_property("cmake_target_name"` - `set_property("cmake_file_name"` - `tools.rmdir(os.path.join(self.package_folder), "lib", "cmake")` - `tools.rmdir(os.path.join(self.package_folder), "share", "cmake")` (unlikely...

with https://github.com/conan-io/conan-center-index/pull/7153 there are some changes to the policy: - `CONAN_LIBS` should be never recommended (will disappear in conan 2.0) - `CONAN_PKG::` should be never recommended (will disappear in conan...

yes, take a look at https://github.com/conan-io/hooks/pull/171, it inspects dylib/otool output I think it should validate the binaries itself, not the cmake files (as there are other build systems than cmake,...

> It's worth noting that I still don't know how to install shared libs with `@rpath` install_name with Meson (currently, all Meson based recipes put absolute path in install_name, like...

> Agree, I just want to say that before adding any hook in conan-center, we should ensure that we have a workaround for all build systems, otherwise it may block...

@uilianries conflicts, please rebase