From f42d8f4cf00d97ffc0038276893ba5d21a8a1599 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 14 Jun 2017 06:59:22 -0700 Subject: documentation: Fixed links for "metadata" term. Fixes [YOCTO #11630] Moving the "Yocto Project Terms" section from the dev-manual to the ref-manual broke the links to the "Metadata" term. I fixed these. (From yocto-docs rev: 190da4b4d44952d141db26ca72b5bc1a52d77023) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/closer-look.xml | 2 +- documentation/ref-manual/migration.xml | 2 +- documentation/ref-manual/ref-bitbake.xml | 4 ++-- documentation/ref-manual/ref-classes.xml | 4 ++-- documentation/ref-manual/ref-features.xml | 2 +- documentation/ref-manual/ref-release-process.xml | 2 +- documentation/ref-manual/ref-structure.xml | 4 ++-- documentation/ref-manual/ref-variables.xml | 10 +++++----- documentation/ref-manual/technical-details.xml | 6 +++--- 9 files changed, 18 insertions(+), 18 deletions(-) (limited to 'documentation/ref-manual') diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml index e4a2a022a7..5046465fba 100644 --- a/documentation/ref-manual/closer-look.xml +++ b/documentation/ref-manual/closer-look.xml @@ -12,7 +12,7 @@ high level. The remainder of this chapter expands on the fundamental input, output, process, and - Metadata) blocks + Metadata) blocks in the Yocto Project development environment. diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml index 5c700bc5ea..b6b067b910 100644 --- a/documentation/ref-manual/migration.xml +++ b/documentation/ref-manual/migration.xml @@ -251,7 +251,7 @@ The following recipes have been removed. For most of them, it is unlikely that you would have any references to them in your own - Metadata. + Metadata. However, you should check your metadata against this list to be sure: libx11-trim: diff --git a/documentation/ref-manual/ref-bitbake.xml b/documentation/ref-manual/ref-bitbake.xml index 2f36e16eaf..9a9499115c 100644 --- a/documentation/ref-manual/ref-bitbake.xml +++ b/documentation/ref-manual/ref-bitbake.xml @@ -8,7 +8,7 @@ BitBake is a program written in Python that interprets the - Metadata used by + Metadata used by the OpenEmbedded build system. At some point, developers wonder what actually happens when you enter: @@ -24,7 +24,7 @@ BitBake strives to be a generic "task" executor that is capable of handling complex dependency relationships. As such, it has no real knowledge of what the tasks being executed actually do. BitBake just considers a list of tasks with dependencies and handles - Metadata + Metadata consisting of variables in a certain format that get passed to the tasks. diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml index 472215c25a..1801faf501 100644 --- a/documentation/ref-manual/ref-classes.xml +++ b/documentation/ref-manual/ref-classes.xml @@ -16,7 +16,7 @@ - Any Metadata usually + Any Metadata usually found in a recipe can also be placed in a class file. Class files are identified by the extension .bbclass and are usually placed in a classes/ directory beneath @@ -2419,7 +2419,7 @@ This check was removed for YP 2.3 release all dependencies previously built. The reason for this discrepancy is because the RPM package manager creates and processes more - Metadata than the + Metadata than the IPK package manager. Consequently, you might consider setting PACKAGE_CLASSES to "package_ipk" if you are diff --git a/documentation/ref-manual/ref-features.xml b/documentation/ref-manual/ref-features.xml index 7e1c5ef2f1..551db6535a 100644 --- a/documentation/ref-manual/ref-features.xml +++ b/documentation/ref-manual/ref-features.xml @@ -36,7 +36,7 @@ One method you can use to determine which recipes are checking to see if a particular feature is contained or not is to grep through - the Metadata + the Metadata for the feature. Here is an example that discovers the recipes whose build is potentially changed based on a given feature: diff --git a/documentation/ref-manual/ref-release-process.xml b/documentation/ref-manual/ref-release-process.xml index fe3ba0933e..aa1ff89a7d 100644 --- a/documentation/ref-manual/ref-release-process.xml +++ b/documentation/ref-manual/ref-release-process.xml @@ -63,7 +63,7 @@ the Yocto Project Source Repositories. The concept is that branches of - Metadata + Metadata with the same codename are likely to be compatible and thus work together. diff --git a/documentation/ref-manual/ref-structure.xml b/documentation/ref-manual/ref-structure.xml index 424b8cc003..3b3f0779cd 100644 --- a/documentation/ref-manual/ref-structure.xml +++ b/documentation/ref-manual/ref-structure.xml @@ -42,7 +42,7 @@ The copy usually matches the current stable BitBake release from the BitBake project. BitBake, a - Metadata + Metadata interpreter, reads the Yocto Project Metadata and runs the tasks defined by that data. Failures are usually from the Metadata and not from BitBake itself. @@ -1023,7 +1023,7 @@ As mentioned previously, - Metadata is the core + Metadata is the core of the Yocto Project. Metadata has several important subdivisions: diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index da4da8550d..632d78aa7e 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -1969,7 +1969,7 @@ Specifies the directory BitBake uses to store a cache of the - Metadata + Metadata so it does not need to be parsed every time BitBake is started. @@ -3455,7 +3455,7 @@ Distribution configuration files are located in a conf/distro directory within the - Metadata + Metadata that contains the distribution configuration. The value for DISTRO must not contain spaces, and is typically all lower-case. @@ -7037,7 +7037,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" Includes additional metadata from the Yocto Project kernel Git repository. In the OpenEmbedded build system, the default Board Support Packages (BSPs) - Metadata + Metadata is provided through the KMACHINE and KBRANCH variables. @@ -7839,7 +7839,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" defines the search arguments used by the kernel tools to find the appropriate description within the kernel - Metadata + Metadata with which to build out the sources and configuration. @@ -12620,7 +12620,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" file:// - Fetches files, which are usually files shipped with the - Metadata, + Metadata, from the local machine. The path is relative to the FILESPATH diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml index 597bfbc55b..768f70186b 100644 --- a/documentation/ref-manual/technical-details.xml +++ b/documentation/ref-manual/technical-details.xml @@ -65,7 +65,7 @@ BitBake is the tool at the heart of the OpenEmbedded build system and is responsible for parsing the - Metadata, + Metadata, generating a list of tasks from it, and then executing those tasks. @@ -152,7 +152,7 @@ Class files (.bbclass) contain information that is useful to share between - Metadata files. + Metadata files. An example is the autotools class, which contains common settings for any application that @@ -610,7 +610,7 @@ The "OEBasicHash" BB_SIGNATURE_HANDLER is the same as the "OEBasic" version but adds the task hash to the stamp files. This results in any - Metadata + Metadata change that changes the task hash, automatically causing the task to be run again. This removes the need to bump PR -- cgit v1.2.3-54-g00ecf