calamares/CMakeModules
Adriaan de Groot f7102527a8 CMake: stop clobbering config files
When CMake runs, configure_file() will clobber the config files in
the build/ directory, which is annoying during testing: you need
to keep making the same edits, or edit the source.

- Introduce new behavior: the config file is **not** overwritten unless
  the source file is newer. This means that edits to config files
  in the build directory are preserved.
- If INSTALL_CONFIG is **on** then the files are clobbered anyway (the
  source is considered new regardless).
..
BoostPython3.cmake CMake: fix boost.python detection on FreeBSD
CMakeColors.cmake CMake: also follow CMAKE_COLOR_MAKEFILE settings
CMakeDateStamp.cmake CMake skeleton.
CMakeVersionSource.cmake CMake skeleton.
CalamaresAddBrandingSubdirectory.cmake CMake: stop overwriting branding settings in the build dir
CalamaresAddLibrary.cmake CMake: switch to autorcc from manual futzing
CalamaresAddModuleSubdirectory.cmake CMake: handle Python modules built from subdirectory a/b
CalamaresAddPlugin.cmake CMake: stop clobbering config files
CalamaresAddTest.cmake [CMakeModules] Update SPDX identifiers.
CalamaresAddTranslations.cmake CMake: simplify QRC generation
CalamaresAutomoc.cmake CMake: switch to autorcc from manual futzing
FindCrypt.cmake Check for crypt(3), also on FreeBSD
FindLIBPARTED.cmake CMake: collect all the Find-modules at top-level
FindLibPWQuality.cmake CMake: fix up warnings from the LibPWQuality module
FindPythonQt.cmake [libcalamaresui] Use PYTHONQT_INCLUDE_DIRS
FindYAMLCPP.cmake CMake: give yamlcpp a proper imported target
IncludeKPMCore.cmake CMake: remove unused module