Packages can now restrict the debian distribution for which they can build using the new 'dists' package key.
This is a csv list of distribution codenames. If the currently building distribution is not in the list then
the package is ignored.
The 'links' section specifies symbolic links which should be added to the package in key : value format.
The key is the source of the link. It must be exist in the filesystem already (as part of the 'files' section)
and be relative to the root of the filesystem.
The value is the name of the link, and can be relative or absolute to the final filesystem.
For example, given that a package produces the real binary "/usr/bin/foobar" and you want /usr/bin/foobar-link -> /usr/bin/foobar
it will be specified as follows:
links:
/usr/bin/foobar : /usr/bin/foobar-link
Some complicated service dependencies will fail to configure
under normal circumstances because invoke-rc.d will kill service
start based on policy-rc.d but this is not taken into account when
configuring services that are dependent on that service.
The dependency check fails prior to the policy-rc.d check and as a result
some packages will remain unconfigured after we have finished constructing
the root filesystem. This is ok for most cases but precludes dynamic modification
of that filesystem post-creation and will even cause
those unconfigured services to be restarted the first time a new package is
installed.
Checking policy-rc.d first in the postinst script allows the configuration
step to complete for all services and their dependents to fix these problems.
The package caches contain paths relative to the distro name (from the $BUILD_DIR variable).
As such the cache can become invalid when switching in-place between distro containers.
Keeping the cache instanced per-container makes sure they don't contaminate each other.
- Support direct release of file products during package builds
- Include suite codename in repo and delivery prefixes in anticipation of multisuite build support.
