We currently use the term package for two different things which will lead to confusion. The work for this ticket is to go through all source-files of the CPF and make sure that comments, function-names, variable-names etc. consistently use the name convention the is described below.
The host-repository that contains root CMakeLists file will be called the deployment-repository.
The toplevel-cmake-project will be called the deployment-project.
The binary archives that can be obtained via package managers are called deployment-packages.
The cmake-projects that are defined in the formerly package CMakeLists file are called module-projects.
The collection of source files that define one production binary target and additional test-targets etc. and that were formerly known as package are now called module-package.
The repository that holds one or multiple module-packages but no top-level CMakeLists file is called the module-repository.
We currently use the term package for two different things which will lead to confusion. The work for this ticket is to go through all source-files of the CPF and make sure that comments, function-names, variable-names etc. consistently use the name convention the is described below.
The host-repository that contains root CMakeLists file will be called the deployment-repository. The toplevel-cmake-project will be called the deployment-project. The binary archives that can be obtained via package managers are called deployment-packages. The cmake-projects that are defined in the formerly package CMakeLists file are called module-projects. The collection of source files that define one production binary target and additional test-targets etc. and that were formerly known as package are now called module-package. The repository that holds one or multiple module-packages but no top-level CMakeLists file is called the module-repository.