blob: ba311b7c1197411fa6b46691b5ce058de8c225b6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
|
This README file contains information on the contents of the cgl layer.
Please see the corresponding sections below for details.
Dependencies
============
This layer depends on:
URI: git://git.yoctoproject.org/poky
branch: master
URI: git://git.openembedded.org/meta-openembedded
layers: meta-oe, meta-perl, meta-networking, meta-filesystems
branch: master
URI: git://git.yoctoproject.org/meta-cloud-services
layers: meta-openstack
branch: master
URI: git://git.yoctoproject.org/meta-qt3
branch: master
URI: https://github.com/joaohf/meta-openclovis
branch: master
URI: git://git.yoctoproject.org/meta-selinux
branch: master
URI: git://git.yoctoproject.org/meta-security
branch: master
URI: git://git.yoctoproject.org/meta-virtualization
branch: master
Source code
===========
git://git.enea.com/linux/meta-cgl.git
Maintenance
===========
Maintainers: Enea Linux Team <linux-maintainers@enea.com>
Contributing
============
Contributions and patches can be sent to the Yocto Project mailing
list: yocto@yoctoproject.org"
As a backup alternative the Enea Linux mailing list can be
used: enealinux@lists.enea.com
When sending patches please take a look at the contribution guide available
here: https://wiki.yoctoproject.org/wiki/Contribution_Guidelines
Table of Contents
=================
I. Adding the cgl layer to your build
II. Misc
III. Layer specific information
IV. Specific terms and information
I. Adding the cgl layer to your build
=================================================
In order to use this layer, you need to make the build system aware of
it.
Assuming the cgl layer exists at the top-level of your
yocto build tree, you can add it to the build system by adding the
location of the cgl layer to bblayers.conf, along with any
other layers needed. Adapt the below list to proper format.
BBLAYERS:
meta
meta-cgl
meta-qt3
meta-openembedded/meta-networking
meta-openembedded/meta-filesystems
meta-openembedded/meta-oe
meta-openembedded/meta-perl
meta-yocto
meta-yocto-bsp
meta-virtualization
meta-openclovis
meta-selinux
meta-security
meta-cloud-services/meta-openstack
A BBMASK definition is required because of some recipes duplicate existance:
BBMASK = "meta-security/recipes-security/libcap-ng|meta-openembedded/meta-oe/recipes-support/multipath-tools"
II. Misc
========
The meta-cgl layer tries to offer CGL compliant packages to be used for
a Linux distribution.
III. Layer specific information
==============================
The layer contains a core package group (packagegroup-cgl.bb) that
should aggregate all the other available package groups.
The recommandation is to group all CGL compliant features into specific
package groups.
An CGL compliant Linux image is also available into the layer. Its use
is to facilitate the development of a CGL compliant OS.
The core image name is: core-image-cgl.bb
IV. Specific terms and information
==================================
HA(high availability) technology - refers to a system or component
that is continuously operational for a long length of time.
Standard interface - represents a joint place of two systems or
subsystems that has a previously agreed upon form so that two systems
may be readily connected together.
Service interface - a programatic interface that tries to achive
interoperability. It enables users to describe independently of a platform
or programming language operations required in the application system at
a later stage.
Interface - shared boundary or connection between two dissimilar
objects, devices or systems.
Users of this layer might experience a problem with openipmi package, if this happens then this
package can be removed from packagegroup-cgl-middleware.bb package group and exclude it from the
image used for building a CGL compliant image.
The latest tested head for the depending layers were:
poky: bb00d83675a1293ee8d7a3ac22cf01243fa2397b
meta-cloud-services: a06e28ced8f622dbe6d6fbd9bea20b215d8ac938
meta-openclovis: 83b1f76a75266743dc9eb0238039d5b973ad8ac0
meta-qt3: 3016129d90b7ac8517a5227d819f10ad417b5b45
meta-security: b3f08c7b2bdf1bea28b081319d7c135af45f39e3
meta-selinux: 1699b56fd801f0194b708b4a1d9d95a831a3bbe4
meta-virtualization: b94455174264240bf8519e4148ea5f1fb38d55c6
The machine for which this layer was tested are: 'qemuppc' and 'p2020rdb'. The latest tested head
for meta-fsl-ppc layer is: d953212ae5936a7d969d13801b0c2c1eb65cee6f
|
