mirror of
https://git.yoctoproject.org/poky
synced 2026-04-21 12:32:15 +02:00
ref-manual: Fixed grammar problem in FILES variable description.
(From yocto-docs rev: faf5bc08e3f015dfb610ebdb73a0747793451033) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
1b7c45eaec
commit
ab3e880f15
@@ -2637,10 +2637,11 @@
|
||||
</para>
|
||||
|
||||
<para>
|
||||
To use the <filename>FILES</filename> variable, provide a package name
|
||||
override that identifies the resulting package.
|
||||
Then, provide a space-separated list of files or paths that identifies the
|
||||
files you want included as part of the resulting package.
|
||||
To use the <filename>FILES</filename> variable, provide a
|
||||
package name override that identifies the resulting package.
|
||||
Then, provide a space-separated list of files or paths
|
||||
that identify the files you want included as part of the
|
||||
resulting package.
|
||||
Here is an example:
|
||||
<literallayout class='monospaced'>
|
||||
FILES_${PN} += "${bindir}/mydir1/ ${bindir}/mydir2/myfile"
|
||||
@@ -2648,24 +2649,29 @@
|
||||
</para>
|
||||
|
||||
<note>
|
||||
When specifying paths as part of the <filename>FILES</filename> variable,
|
||||
it is good practice to use appropriate path variables.
|
||||
For example, use <filename>${sysconfdir}</filename> rather than
|
||||
<filename>/etc</filename>, or <filename>${bindir}</filename> rather
|
||||
than <filename>/usr/bin</filename>.
|
||||
When specifying paths as part of the
|
||||
<filename>FILES</filename> variable, it is good practice
|
||||
to use appropriate path variables.
|
||||
For example, use <filename>${sysconfdir}</filename> rather
|
||||
than <filename>/etc</filename>, or
|
||||
<filename>${bindir}</filename> rather than
|
||||
<filename>/usr/bin</filename>.
|
||||
You can find a list of these variables at the top of the
|
||||
<filename>meta/conf/bitbake.conf</filename> file in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
|
||||
</note>
|
||||
|
||||
<para>
|
||||
If some of the files you provide with the <filename>FILES</filename> variable
|
||||
are editable and you know they should not be
|
||||
overwritten during the package update process by the Package Management
|
||||
System (PMS), you can identify these files so that the PMS will not
|
||||
If some of the files you provide with the
|
||||
<filename>FILES</filename> variable are editable and you
|
||||
know they should not be overwritten during the package
|
||||
update process by the Package Management System (PMS), you
|
||||
can identify these files so that the PMS will not
|
||||
overwrite them.
|
||||
See the <filename><link linkend='var-CONFFILES'>CONFFILES</link></filename>
|
||||
variable for information on how to identify these files to the PMS.
|
||||
See the
|
||||
<link linkend='var-CONFFILES'><filename>CONFFILES</filename></link>
|
||||
variable for information on how to identify these files to
|
||||
the PMS.
|
||||
</para>
|
||||
|
||||
</glossdef>
|
||||
|
||||
Reference in New Issue
Block a user