To ensure that boost remains an empty metapackage after version
updates, we explicitly require boost files to be empty. If new
libraries exist after a version update of the boost recipe,
bitbake will emit a warning at the do_package task. For example,
at the version update from 1.58.0 to 1.59.0, th
> On Jan 5, 2016, at 1:32 AM, Lukas Bulwahn
> wrote:
>
> To ensure that boost remains an empty metapackage after version
> updates, we explicitly require boost files to be empty. If new
> libraries exist after a version update of the boost recipe,
> bitbake will emit a warning at the do_package
