[yocto-ab] YP Advisory Board: OTE: Enea Linux 6 YP Compatible

Philip Balister philip at balister.org
Tue Sep 6 12:45:11 PDT 2016


Yes from OpenEmbedded

On 09/05/2016 03:20 PM, Jeff Osier-Mixon wrote:
> Hi folks - please vote on Enea's latest version to be YP Compatible - thanks
> 
>  --Contact information--
>      Organization: Enea Software
>      Project name: Enea LInux 6.0
>      Contact name: Dejan Bucar
>      Contact email address: dejan.bucar at enea.com
>      URL to organization or product link:
>      http://www.enea.com/solutions/Enea-Linux/
>      Registration date: 2016-08-24
>      Compliance Agreement revision: 1.0
>      Yocto Project Compatible Version: 2.1
> 
> 
> Acceptance Criteria:
>   - Working towards and supporting the aims and objectives of the Yocto
> Project. These include decreasing the fragmentation of embedded ecosystem and
> focus around a common shared set of tools, formats and best practices. We
> want to avoid multiple groups of people repeating the same work and have one
> set of great tools rather than multiple tools with drawbacks.: Yes
>   - Promoting the OpenEmbedded architecture, layer model, and BSP format.:Yes
>   - Making visible contributions in the OpenEmbedded and component projectsof
> the Yocto Project. Please describe your participation in the comments section
> below.: Yes
>   - Are all your publicly accessible layers listed in the OpenEmbedded Layers
> index (http://layers.openembedded.org)?: Yes
>   - Be a non-profit, or member of the Yocto Project working group, regardless
> of organization size, or if the project's parent organization is an
> open-source project.: Yes
>   - If the project includes build system functionality, are BitBake and
> OpenEmbedded-Core included as components?: Yes
>   - If present, can the directories containing BitBake and OpenEmbedded-Core
> be clearly identified within the system and only contain those components?:
> Yes
>   - Have all patches applied to BitBake and OpenEmbedded-Core (if present)
> been submitted to the open source community?: Yes
>   - Do all layers contain a README file which details the origin of thelayer,
> its maintainer, where to submit changes, and any dependencies or version
> requirements?: Yes
>   - Do all layers build without errors against OpenEmbedded-Core with onlythe
> dependencies/requirements listed in their README file?: Yes
>   - (For BSPs) Does the layer follow the format defined in the Yocto Project
> Board Support Package (BSP) Developers Guide?: Yes
>   - Are hardware support, configuration (distro) policy, and recipe metadata
> separated into different layers which do not depend on each other?: Yes
>   - Is a test report document included showing which combinations of layers,
> recipes, and machines have been tested?: Yes
>   - If any item in the "Yocto Project Compatible Compliance Recommendations"
> list is not true, is this documented in the testing report?: Yes
> Recommendations:
>   - Linux kernels are either based around LTSI kernel versions or a Yocto
> Project kernel version.: Yes
>   - Everything builds successfully with the standard toolchain from OE-Core,
> where the architecture is one supported by OE-Core as standard. This is to
> ensure that your layers are compatible with OE-Core. It is not required that
> the OE-Core toolchain be provided to customers or any downstream projects.:
> Yes
> Explanation:
> Hi,
> 
> Our webpage is not updated yet with  Enea Linux 6  but it is available
> through our public git repos,
> http://git.enea.com/cgit/linux/el_manifests-standard.git/
> 
> Br,
> Dejan
> 



More information about the yocto-ab mailing list