[Buildroot] [PATCH 3/4] docs/manual: document FOO_PERMISSIONS_FILE

Matthew Weber matthew.weber at rockwellcollins.com
Mon Mar 27 16:44:55 UTC 2017


Thomas,

On Sun, Mar 26, 2017 at 4:43 PM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> From: "Yann E. MORIN" <yann.morin.1998 at free.fr>
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998 at free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
> Cc: Peter Korsgaard <peter at korsgaard.com>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
> ---
>  docs/manual/adding-packages-generic.txt | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt
> index a08283c..23b07fa 100644
> --- a/docs/manual/adding-packages-generic.txt
> +++ b/docs/manual/adding-packages-generic.txt
> @@ -386,7 +386,13 @@ information is (assuming the package name is +libfoo+) :
>  * +LIBFOO_PERMISSIONS+ lists the changes of permissions to be done at
>    the end of the build process. The syntax is once again the makedevs one.
>    You can find some documentation for this syntax in the xref:makedev-syntax[].
> -  This variable is optional.
> +  This variable is optional; its value must be known when the .mk file
> +  is parsed.
> +
> +* +LIBFOO_PERMISSIONS_FILE+, like +LIBFOO_PERMISSIONS+ but points to a
> +  file that contains the list of permissions. Unlike +LIBFOO_PERMISSIONS+,
> +  its content need not be known when the .mk file is parsed, so it can be
> +  generated. This variable is optional, and you should seldom need it.
>
>  * +LIBFOO_USERS+ lists the users to create for this package, if it installs
>    a program you want to run as a specific user (e.g. as a daemon, or as a

Reviewed-by: Matt Weber <matthew.weber at rockwellcollins.com>



More information about the buildroot mailing list