On Thu, Mar 8, 2018 at 6:23 PM, Christopher Clark <
christopher.w.clark@gmail.com> wrote:

>
> On Mon, Mar 5, 2018 at 7:35 AM, Kurt Bodiker <kurt.bodiker@braintrust-us.
> com> wrote:
>
>> From: kebodiker <kurt.bodiker@braintrust-us.com>
>>
>> This commit introduces the stubdom.inc file that is required for each
>> recipe that is/will be built for Xen stubdomains.
>>
>
>
>
>> +# Couldn't find any other way to access the version of Xen used as a
>> dependency.
>> +# This version number needs changed to match version of Xen recipe  used
>> in builds.
>> +XEN_VERSION = "4.9.0"
>>
>
>
> :( I understand the challenge here and sadly I don't have a better
> recommendation, but: would putting a scope on the DEPEND enable the build
> to fail fast in case
> of a mismatch?  ie:
>
>     DEPENDS = "xen (= ${XEN_VERSION}-r0)"
>
>
In testing, this constraint of package version doesn't produce the build
behaviour I was hoping for: bitbake doesn't enforce the version constraint
at build time and from earlier related posts on the mailing list, this
behaviour is known, so presumably is intentional.

So: I'll retract the review comment above - ie. there's no need to touch
DEPENDS - and the XEN_VERSION variable definition going into the stubdom
recipe seems practical and reasonable.

Christopher