# daq-sw-librarians discussion on 09/03

## Instructions for release building

* Instructions for building a DAQ release from scratch (meaning with only externals provided by 3rd party):
1. building DAQ owned externals;
2. building DAQ packages.

## Release manifest file
* Handling release with release manifest file(s):
1. for building a release with pre-built externals and DAQ source packages;
2. for setting up a release with all pre-built packages;
3. for handling different flavors of packages.

## CMake modules support
* Additional functionalities in CMake modules:
1. ~~checking the existence of desired flavor of packages;~~
2. support for multi-package development environment (Pengfei’s words, handling base release vs test release; ensure test release overriding base release);
* propose a new file (like product_deps) to be associated with each package, in which the package's dependencies are listed. This can be used by a build script to find out the order of building package in the multi-pacakge dev env.
3. (Possible solution for CMake’s support for multi-package development env: consolidate the multi-packages into one big CMake project, so make rules will auto resolve building orders.)