summaryrefslogtreecommitdiffstats
path: root/scripts/postinst-intercepts/update_gtk_immodules_cache
diff options
context:
space:
mode:
authorKosta Zertsekel <zertsekel@gmail.com>2018-11-04 21:24:46 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-11-07 23:08:55 +0000
commit92027161b5a4cb22e8f3f7fb5bd1bdd1babd2cfc (patch)
tree0b1b43383c27544743b8aaf2453d5cbf787cf759 /scripts/postinst-intercepts/update_gtk_immodules_cache
parentff842fe7771e399498264e14fa04a1d7935322a3 (diff)
downloadpoky-92027161b5a4cb22e8f3f7fb5bd1bdd1babd2cfc.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) 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>
Diffstat (limited to 'scripts/postinst-intercepts/update_gtk_immodules_cache')
0 files changed, 0 insertions, 0 deletions