[yocto] inheriting native.bbclass explicitly

[Dudziak Krzysztof]

Current release's reference manual issues in native.bbclass chapter a warning:
"When creating a recipe, you must follow this naming convention:      native-myrecipe.bb
Not doing so can lead to subtle problems because code exists that depends on the naming convention."

Jethro release manual does not point it out.
Is this warning really out of relevance for certain past releases e.g. Jethro?

Abstracting from question raised above how following two fit all together:
"When creating a recipe, you must follow this naming convention:      native-myrecipe.bb"
and
" The advantage of the second method is that you do not need to have two separate recipes " (2.5.1 Release Reference Manual)

krzysiek

-----Original Message-----
From: Burton, Ross [mailto:ross.burton at intel.com]
Sent: Thursday, 13. September 2018 14:00
To: Dudziak Krzysztof <Krzysztof.Dudziak at gemalto.com>
Cc: yocto at yoctoproject.org
Subject: Re: [yocto] inheriting native.bbclass explicitly

On 13 September 2018 at 12:39, Dudziak Krzysztof
<Krzysztof.Dudziak at gemalto.com> wrote:
> Thanks for hints.
> I don't want to have this package on target system.
> You sound like inheriting explicitly had some major drawback of wide scope.

It won't be included in the image unless you add it to the image.

Ross
________________________________
 This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.