Please don't include GCC version in installed file paths

[yurivict]

This and many your other projects include strings like GNU-10.3.0:

$ find /usr/local/include/ -name GNU-10.3.0
/usr/local/include/mctc-lib/GNU-10.3.0
/usr/local/include/mstore/GNU-10.3.0
/usr/local/include/multicharge/GNU-10.3.0
/usr/local/include/toml-f/GNU-10.3.0
/usr/local/include/tblite/GNU-10.3.0
/usr/local/include/s-dftd3/GNU-10.3.0
/usr/local/include/dftd4/GNU-10.3.0

This causes ports/packages to break when gcc version is changed because plist would change and ports would need to be updated.

[awvwgk]

Since Fortran compiler are not necessarily ABI compatible this is the wanted behavior.

However, it is notable that the GFortran ABI has been stable now since version 9, meaning this could be reconsidered now. I'm unsure whether there is a reliable way to extract the version of the module files at configure time to use this for tagging rather than the compiler version number which might be too tightly pinned.

[awvwgk]

The module directory is set always in config/CMakeLists.txt:

toml-f/config/CMakeLists.txt

Lines 16 to 20 in f066ec6

	set(
	module-dir
	"${PROJECT_NAME}/${CMAKE_Fortran_COMPILER_ID}-${CMAKE_Fortran_COMPILER_VERSION}"
	)
	set(module-dir "${module-dir}" PARENT_SCOPE)

feel free to patch the generation of the module directory string if this is an actual problem. I could also offer in the future to allow overwriting a cached variable.