Move the Profile Specific Release directory data into the appropriate Profile directory. Add a build-tool that copies this release information from the appropriate Profile Release directory into the common Release directory during build as part of the make checkout: –and– update: just after the point where the data has been updated.
A checkout prior to this point will yield:
* The Common Release directory contains the release information for multiple Profiles making it non-generic
* The Release directory was laid out in Version Product Build order instead of Product Version Build order, which is more intuitive because generally a Build belongs to a Version, which belongs to a Product
Move the Profile Specific Release directory data into the appropriate Profile directory. Add a build-tool that copies this release information from the appropriate Profile Release directory into the common Release directory during build as part of the make checkout: –and– update: just after the point where the data has been updated.
A checkout prior to this point will yield:
* The Common Release directory contains the release information for multiple Profiles making it non-generic
* The Release directory was laid out in Version Product Build order instead of Product Version Build order, which is more intuitive because generally a Build belongs to a Version, which belongs to a Product
Also:
- commit previously ommited files in build/profiles/default
- make jail.pyd per-profile configuration file
- add support for multiple port overlay trees
- make update package templates use external filelists with @include directives
* Build profiles are stored in build/profiles/ directory (one subdirectory per profile)
* Main profile config file is called config.pyd
* Profiles other than default should inherit default profile config and modify it
* DSL syntax changed to more readable and more flexible
