diff options
Diffstat (limited to 'documentation/poky-ref-manual/migration.xml')
-rw-r--r-- | documentation/poky-ref-manual/migration.xml | 148 |
1 files changed, 74 insertions, 74 deletions
diff --git a/documentation/poky-ref-manual/migration.xml b/documentation/poky-ref-manual/migration.xml index b311da65c5..40c570f8ca 100644 --- a/documentation/poky-ref-manual/migration.xml +++ b/documentation/poky-ref-manual/migration.xml | |||
@@ -6,8 +6,8 @@ | |||
6 | <title>Migrating to a Newer Yocto Project Release</title> | 6 | <title>Migrating to a Newer Yocto Project Release</title> |
7 | 7 | ||
8 | <para> | 8 | <para> |
9 | This chapter provides information you can use to migrate work to a | 9 | This chapter provides information you can use to migrate work to a |
10 | newer Yocto Project release. You can find the same information in the | 10 | newer Yocto Project release. You can find the same information in the |
11 | release notes for a given release. | 11 | release notes for a given release. |
12 | </para> | 12 | </para> |
13 | 13 | ||
@@ -15,7 +15,7 @@ | |||
15 | <title>Moving to the Yocto Project 1.3 Release</title> | 15 | <title>Moving to the Yocto Project 1.3 Release</title> |
16 | 16 | ||
17 | <para> | 17 | <para> |
18 | This section provides migration information for moving to the | 18 | This section provides migration information for moving to the |
19 | Yocto Project 1.3 Release. | 19 | Yocto Project 1.3 Release. |
20 | </para> | 20 | </para> |
21 | 21 | ||
@@ -23,7 +23,7 @@ | |||
23 | <title>Local Configuration</title> | 23 | <title>Local Configuration</title> |
24 | 24 | ||
25 | <para> | 25 | <para> |
26 | Differences include changes for | 26 | Differences include changes for |
27 | <link linkend='var-SSTATE_MIRRORS'><filename>SSTATE_MIRRORS</filename></link> | 27 | <link linkend='var-SSTATE_MIRRORS'><filename>SSTATE_MIRRORS</filename></link> |
28 | and <filename>bblayers.conf</filename>. | 28 | and <filename>bblayers.conf</filename>. |
29 | </para> | 29 | </para> |
@@ -32,18 +32,18 @@ | |||
32 | <title>SSTATE_MIRRORS</title> | 32 | <title>SSTATE_MIRRORS</title> |
33 | 33 | ||
34 | <para> | 34 | <para> |
35 | The shared state cache (sstate-cache) as pointed to by | 35 | The shared state cache (sstate-cache) as pointed to by |
36 | <link linkend='var-SSTATE_DIR'><filename>SSTATE_DIR</filename></link> by default | 36 | <link linkend='var-SSTATE_DIR'><filename>SSTATE_DIR</filename></link> by default |
37 | now has two-character subdirectories to prevent there being an issue with too | 37 | now has two-character subdirectories to prevent there being an issue with too |
38 | many files in the same directory. | 38 | many files in the same directory. |
39 | Also, native sstate-cache packages will go into a subdirectory named using | 39 | Also, native sstate-cache packages will go into a subdirectory named using |
40 | the distro ID string. | 40 | the distro ID string. |
41 | If you copy the newly structured sstate-cache to a mirror location | 41 | If you copy the newly structured sstate-cache to a mirror location |
42 | (either local or remote) and then point to it in | 42 | (either local or remote) and then point to it in |
43 | <link linkend='var-SSTATE_MIRRORS'><filename>SSTATE_MIRRORS</filename></link>, | 43 | <link linkend='var-SSTATE_MIRRORS'><filename>SSTATE_MIRRORS</filename></link>, |
44 | you need to append "PATH" to the end of the mirror URL so that | 44 | you need to append "PATH" to the end of the mirror URL so that |
45 | the path used by BitBake before the mirror substitution is | 45 | the path used by BitBake before the mirror substitution is |
46 | appended to the path used to access the mirror. | 46 | appended to the path used to access the mirror. |
47 | Here is an example: | 47 | Here is an example: |
48 | <literallayout class='monospaced'> | 48 | <literallayout class='monospaced'> |
49 | SSTATE_MIRRORS = "file://.* http://someserver.tld/share/sstate/PATH" | 49 | SSTATE_MIRRORS = "file://.* http://someserver.tld/share/sstate/PATH" |
@@ -55,14 +55,14 @@ | |||
55 | <title>bblayers.conf</title> | 55 | <title>bblayers.conf</title> |
56 | 56 | ||
57 | <para> | 57 | <para> |
58 | The <filename>meta-yocto</filename> layer has been split into | 58 | The <filename>meta-yocto</filename> layer has been split into |
59 | two parts: <filename>meta-yocto</filename> and | 59 | two parts: <filename>meta-yocto</filename> and |
60 | <filename>meta-yocto-bsp</filename>, corresponding to the | 60 | <filename>meta-yocto-bsp</filename>, corresponding to the |
61 | Poky reference distro configuration and the reference | 61 | Poky reference distro configuration and the reference |
62 | hardware Board Support Packages (BSPs), respectively. | 62 | hardware Board Support Packages (BSPs), respectively. |
63 | When running BitBake or Hob for the first time after upgrading, | 63 | When running BitBake or Hob for the first time after upgrading, |
64 | your <filename>conf/bblayers.conf</filename> file will be | 64 | your <filename>conf/bblayers.conf</filename> file will be |
65 | updated to handle this change and you will be asked to | 65 | updated to handle this change and you will be asked to |
66 | re-run/restart for the changes to take effect. | 66 | re-run/restart for the changes to take effect. |
67 | </para> | 67 | </para> |
68 | </section> | 68 | </section> |
@@ -87,16 +87,16 @@ | |||
87 | <title>Python Function Whitespace</title> | 87 | <title>Python Function Whitespace</title> |
88 | 88 | ||
89 | <para> | 89 | <para> |
90 | All Python functions must now use four spaces for indentation. | 90 | All Python functions must now use four spaces for indentation. |
91 | Previously, an inconsistent mix of spaces and tabs existed, | 91 | Previously, an inconsistent mix of spaces and tabs existed, |
92 | which made extending these functions using | 92 | which made extending these functions using |
93 | <filename>_append</filename> or <filename>_prepend</filename> | 93 | <filename>_append</filename> or <filename>_prepend</filename> |
94 | complicated given that Python treats whitespace as | 94 | complicated given that Python treats whitespace as |
95 | syntactically significant. | 95 | syntactically significant. |
96 | If you are defining or extending any Python functions (e.g. | 96 | If you are defining or extending any Python functions (e.g. |
97 | <filename>populate_packages</filename>, <filename>do_unpack</filename>, | 97 | <filename>populate_packages</filename>, <filename>do_unpack</filename>, |
98 | <filename>do_patch</filename> and so forth) in custom recipes | 98 | <filename>do_patch</filename> and so forth) in custom recipes |
99 | or classes, you need to ensure you are using consistent | 99 | or classes, you need to ensure you are using consistent |
100 | four-space indentation. | 100 | four-space indentation. |
101 | </para> | 101 | </para> |
102 | </section> | 102 | </section> |
@@ -105,7 +105,7 @@ | |||
105 | <title>proto= in SRC_URI</title> | 105 | <title>proto= in SRC_URI</title> |
106 | 106 | ||
107 | <para> | 107 | <para> |
108 | Any use of <filename>proto=</filename> in | 108 | Any use of <filename>proto=</filename> in |
109 | <link linkend='var-SRC_URI'><filename>SRC_URI</filename></link> | 109 | <link linkend='var-SRC_URI'><filename>SRC_URI</filename></link> |
110 | needs to be changed to <filename>protocol=</filename>. | 110 | needs to be changed to <filename>protocol=</filename>. |
111 | In particular, this applies to the following URIs: | 111 | In particular, this applies to the following URIs: |
@@ -125,11 +125,11 @@ | |||
125 | 125 | ||
126 | <para> | 126 | <para> |
127 | The suffix <filename>nativesdk</filename> is now implemented | 127 | The suffix <filename>nativesdk</filename> is now implemented |
128 | as a prefix, which simplifies a lot of the packaging code for | 128 | as a prefix, which simplifies a lot of the packaging code for |
129 | <filename>nativesdk</filename> recipes. | 129 | <filename>nativesdk</filename> recipes. |
130 | All custom <filename>nativesdk</filename> recipes and any | 130 | All custom <filename>nativesdk</filename> recipes and any |
131 | references need to be updated to use | 131 | references need to be updated to use |
132 | <filename>nativesdk-*</filename> instead of | 132 | <filename>nativesdk-*</filename> instead of |
133 | <filename>*-nativesdk</filename>. | 133 | <filename>*-nativesdk</filename>. |
134 | </para> | 134 | </para> |
135 | </section> | 135 | </section> |
@@ -138,25 +138,25 @@ | |||
138 | <title>Task Recipes</title> | 138 | <title>Task Recipes</title> |
139 | 139 | ||
140 | <para> | 140 | <para> |
141 | "Task" recipes are now known as "Package groups" and have | 141 | "Task" recipes are now known as "Package groups" and have |
142 | been renamed from <filename>task-*.bb</filename> to | 142 | been renamed from <filename>task-*.bb</filename> to |
143 | <filename>packagegroup-*.bb</filename>. | 143 | <filename>packagegroup-*.bb</filename>. |
144 | Existing references to the previous <filename>task-*</filename> | 144 | Existing references to the previous <filename>task-*</filename> |
145 | names should work in most cases as there is an automatic | 145 | names should work in most cases as there is an automatic |
146 | upgrade path for most packages. | 146 | upgrade path for most packages. |
147 | However, you should update references in your own recipes and | 147 | However, you should update references in your own recipes and |
148 | configurations as they could be removed in future releases. | 148 | configurations as they could be removed in future releases. |
149 | You should also rename any custom <filename>task-*</filename> | 149 | You should also rename any custom <filename>task-*</filename> |
150 | recipes to <filename>packagegroup-*</filename>, and change | 150 | recipes to <filename>packagegroup-*</filename>, and change |
151 | them to inherit <filename>packagegroup</filename> instead of | 151 | them to inherit <filename>packagegroup</filename> instead of |
152 | <filename>task</filename>, as well as taking the opportunity | 152 | <filename>task</filename>, as well as taking the opportunity |
153 | to remove anything now handled by | 153 | to remove anything now handled by |
154 | <filename>packagegroup.bbclass</filename>, such as providing | 154 | <filename>packagegroup.bbclass</filename>, such as providing |
155 | <filename>-dev</filename> and <filename>-dbg</filename> | 155 | <filename>-dev</filename> and <filename>-dbg</filename> |
156 | packages, setting | 156 | packages, setting |
157 | <link linkend='var-LIC_FILES_CHKSUM'><filename>LIC_FILES_CHKSUM</filename></link>, | 157 | <link linkend='var-LIC_FILES_CHKSUM'><filename>LIC_FILES_CHKSUM</filename></link>, |
158 | and so forth. | 158 | and so forth. |
159 | See the | 159 | See the |
160 | "<link linkend='ref-classes-packagegroup'>Package Groups - packagegroup.bbclass</link>" | 160 | "<link linkend='ref-classes-packagegroup'>Package Groups - packagegroup.bbclass</link>" |
161 | section for further details. | 161 | section for further details. |
162 | </para> | 162 | </para> |
@@ -166,13 +166,13 @@ | |||
166 | <title>IMAGE_FEATURES</title> | 166 | <title>IMAGE_FEATURES</title> |
167 | 167 | ||
168 | <para> | 168 | <para> |
169 | Image recipes that previously included "apps-console-core" | 169 | Image recipes that previously included "apps-console-core" |
170 | in <link linkend='var-IMAGE_FEATURES'><filename>IMAGE_FEATURES</filename></link> | 170 | in <link linkend='var-IMAGE_FEATURES'><filename>IMAGE_FEATURES</filename></link> |
171 | should now include "splash" instead to enable the boot-up | 171 | should now include "splash" instead to enable the boot-up |
172 | splash screen. | 172 | splash screen. |
173 | Retaining "apps-console-core" will still include the splash | 173 | Retaining "apps-console-core" will still include the splash |
174 | screen generates a warning. | 174 | screen generates a warning. |
175 | The "apps-x11-core" and "apps-x11-games" | 175 | The "apps-x11-core" and "apps-x11-games" |
176 | <filename>IMAGE_FEATURES</filename> features have been removed. | 176 | <filename>IMAGE_FEATURES</filename> features have been removed. |
177 | </para> | 177 | </para> |
178 | </section> | 178 | </section> |
@@ -181,55 +181,55 @@ | |||
181 | <title>Removed Recipes</title> | 181 | <title>Removed Recipes</title> |
182 | 182 | ||
183 | <para> | 183 | <para> |
184 | The following recipes have been removed. | 184 | The following recipes have been removed. |
185 | For most of them, it is unlikely that you would have any | 185 | For most of them, it is unlikely that you would have any |
186 | references to them in your own metadata. | 186 | references to them in your own metadata. |
187 | However, you should check your metadata against this list to be sure: | 187 | However, you should check your metadata against this list to be sure: |
188 | <itemizedlist> | 188 | <itemizedlist> |
189 | <listitem><para><emphasis><filename>libx11-trim</filename></emphasis>: | 189 | <listitem><para><emphasis><filename>libx11-trim</filename></emphasis>: |
190 | Replaced by <filename>libx11</filename>, which has a negligible | 190 | Replaced by <filename>libx11</filename>, which has a negligible |
191 | size difference with modern Xorg.</para></listitem> | 191 | size difference with modern Xorg.</para></listitem> |
192 | <listitem><para><emphasis><filename>xserver-xorg-lite</filename></emphasis>: | 192 | <listitem><para><emphasis><filename>xserver-xorg-lite</filename></emphasis>: |
193 | Use <filename>xserver-xorg</filename>, which has a negligible | 193 | Use <filename>xserver-xorg</filename>, which has a negligible |
194 | size difference when DRI and GLX modules are not installed.</para></listitem> | 194 | size difference when DRI and GLX modules are not installed.</para></listitem> |
195 | <listitem><para><emphasis><filename>xserver-kdrive</filename></emphasis>: | 195 | <listitem><para><emphasis><filename>xserver-kdrive</filename></emphasis>: |
196 | Effectively unmaintained for many years.</para></listitem> | 196 | Effectively unmaintained for many years.</para></listitem> |
197 | <listitem><para><emphasis><filename>mesa-xlib</filename></emphasis>: | 197 | <listitem><para><emphasis><filename>mesa-xlib</filename></emphasis>: |
198 | No longer serves any purpose.</para></listitem> | 198 | No longer serves any purpose.</para></listitem> |
199 | <listitem><para><emphasis><filename>galago</filename></emphasis>: | 199 | <listitem><para><emphasis><filename>galago</filename></emphasis>: |
200 | Replaced by telepathy.</para></listitem> | 200 | Replaced by telepathy.</para></listitem> |
201 | <listitem><para><emphasis><filename>gail</filename></emphasis>: | 201 | <listitem><para><emphasis><filename>gail</filename></emphasis>: |
202 | Functionality was integrated into GTK+ 2.13.</para></listitem> | 202 | Functionality was integrated into GTK+ 2.13.</para></listitem> |
203 | <listitem><para><emphasis><filename>eggdbus</filename></emphasis>: | 203 | <listitem><para><emphasis><filename>eggdbus</filename></emphasis>: |
204 | No longer needed.</para></listitem> | 204 | No longer needed.</para></listitem> |
205 | <listitem><para><emphasis><filename>gcc-*-intermediate</filename></emphasis>: | 205 | <listitem><para><emphasis><filename>gcc-*-intermediate</filename></emphasis>: |
206 | The build has been restructured to avoid the need for | 206 | The build has been restructured to avoid the need for |
207 | this step.</para></listitem> | 207 | this step.</para></listitem> |
208 | <listitem><para><emphasis><filename>libgsmd</filename></emphasis>: | 208 | <listitem><para><emphasis><filename>libgsmd</filename></emphasis>: |
209 | Unmaintained for many years. | 209 | Unmaintained for many years. |
210 | Functionality now provided by | 210 | Functionality now provided by |
211 | <filename>ofono</filename> instead.</para></listitem> | 211 | <filename>ofono</filename> instead.</para></listitem> |
212 | <listitem><para><emphasis>contacts, dates, tasks, eds-tools</emphasis>: | 212 | <listitem><para><emphasis>contacts, dates, tasks, eds-tools</emphasis>: |
213 | Largely unmaintained PIM application suite. | 213 | Largely unmaintained PIM application suite. |
214 | It has been moved to <filename>meta-gnome</filename> | 214 | It has been moved to <filename>meta-gnome</filename> |
215 | in <filename>meta-openembedded</filename>.</para></listitem> | 215 | in <filename>meta-openembedded</filename>.</para></listitem> |
216 | </itemizedlist> | 216 | </itemizedlist> |
217 | In addition to the previously listed changes, the | 217 | In addition to the previously listed changes, the |
218 | <filename>meta-demoapps</filename> directory has also been removed | 218 | <filename>meta-demoapps</filename> directory has also been removed |
219 | because the recipes in it were not being maintained and many | 219 | because the recipes in it were not being maintained and many |
220 | had become obsolete or broken. | 220 | had become obsolete or broken. |
221 | Additionally, these recipes were not parsed in the default configuration. | 221 | Additionally, these recipes were not parsed in the default configuration. |
222 | Many of these recipes are already provided in an updated and | 222 | Many of these recipes are already provided in an updated and |
223 | maintained form within OpenEmbedded community layers such as | 223 | maintained form within OpenEmbedded community layers such as |
224 | <filename>meta-oe</filename> and <filename>meta-gnome</filename>. | 224 | <filename>meta-oe</filename> and <filename>meta-gnome</filename>. |
225 | For the remainder, you can now find them in the | 225 | For the remainder, you can now find them in the |
226 | <filename>meta-extras</filename> repository, which is in the | 226 | <filename>meta-extras</filename> repository, which is in the |
227 | Yocto Project source repositories. | 227 | Yocto Project source repositories. |
228 | </para> | 228 | </para> |
229 | </section> | 229 | </section> |
230 | </section> | 230 | </section> |
231 | </section> | 231 | </section> |
232 | </chapter> | 232 | </chapter> |
233 | <!-- | 233 | <!-- |
234 | vim: expandtab tw=80 ts=4 | 234 | vim: expandtab tw=80 ts=4 |
235 | --> | 235 | --> |