diff options
author | Kosta Zertsekel <zertsekel@gmail.com> | 2018-11-04 21:24:46 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-11-24 21:45:58 +0000 |
commit | 52db6681b25342ba3ee336a777594e0a59a84d78 (patch) | |
tree | 1df9dfc2e9e3e0e507d5230258d6c2ef51e6aad0 /meta/recipes-graphics/xorg-app | |
parent | 5ed5ca2f03ddb7e678b428c10674dd0b91cf64a0 (diff) | |
download | poky-52db6681b25342ba3ee336a777594e0a59a84d78.tar.gz |
meta: Use double colon for chown OWNER:GROUP
Rationale - excerp from `info chown`
====================================
OWNER‘:’GROUP
If the OWNER is followed by a colon and a GROUP (a group name or
numeric group ID), with no spaces between them, the group ownership
of the files is changed as well (to GROUP).
Some older scripts may still use ‘.’ in place of the ‘:’ separator.
POSIX 1003.1-2001 (*note Standards conformance::) does not require
support for that, but for backward compatibility GNU ‘chown’ supports
‘.’ so long as no ambiguity results. New scripts should avoid the use
of ‘.’ because it is not portable, and because it has undesirable
results if the entire OWNER‘.’GROUP happens to identify a user whose
name contains ‘.’.
(From OE-Core rev: 185918234a07cb506d7d7464a49ac33972c7d963)
(From OE-Core rev: 8105b6384042e04d8bdfaa881370616c6e46acfa)
Signed-off-by: Kosta Zertsekel <zertsekel@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-graphics/xorg-app')
0 files changed, 0 insertions, 0 deletions