No standard way for third party packages to install cmake modules in a directory obviously connected with cmake
Third party libraries which want to be easy to use usually install .pc files to one of a small number of standard locations (e.g. /usr/lib/pkgconfig/myLib.pc ), for easy use by pkg-config.
Developers expect cmake to search a similar list of standard locations (e.g. /usr/share/cmake/Modules) for e.g. FindMyLib.cmake. Cmake almost does this... but for include() the list of standard locations is version-dependent and length one (e.g. /usr/share/cmake-3.6/Modules), so there is no way for a third party package to install a module that is visible regardless of version of cmake used. And for find_package(), the list of standard locations is huge and does not include anything with the word 'cmake' in it.
Standard practice for cmake has been to ship modules to find everything itself, but this does not scale especially well in all cases.
So: please predefine a list of standard system locations that will always be searched for packages, and support it on all systems (or at least Windows, Mac, and Linux).... and please make it simple, without the uuids and indirection in the existing windows system package registry.
The simplest solution might be to add the location /usr/share/cmake/Modules to the existing list for find_packages...?