]> code.ossystems Code Review - openembedded-core.git/commit
meta: Use double colon for chown OWNER:GROUP
authorKosta Zertsekel <zertsekel@gmail.com>
Sun, 4 Nov 2018 19:24:46 +0000 (21:24 +0200)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 6 Nov 2018 12:14:24 +0000 (12:14 +0000)
commit185918234a07cb506d7d7464a49ac33972c7d963
tree2c4957c114fb8e4dc4edf9f42e6163f540508b62
parent82f9157e84dcaf0ad4292053b09be68c2290d197
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 ‘.’.

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>
meta/recipes-core/images/build-appliance-image_15.0.0.bb
meta/recipes-core/initscripts/initscripts-1.0/populate-volatile.sh
meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb