openembedded-core.git/meta-skeleton/recipes-skeleton/useradd, branch master Mirror of openembedded-core useradd-example: exclude from world 2017-01-09T13:34:29+00:00 Kai Kang kai.kang@windriver.com 2016-12-22T09:55:16+00:00 1e03ad25d8b9536d5e7f9969809a4df01e55fe3a Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Remove $COREBASE/LICENSE from LIC_FILES_CHKSUM 2016-10-28T10:27:33+00:00 Olaf Mandel o.mandel@menlosystems.com 2016-10-21T09:24:28+00:00 0059e0661826c857a07c862bcb46162671e0e330 Several recipes reference the LICENSE file in their LIC_FILES_CHKSUM variable as ${COREBASE}/LICENSE. This forces distribution providers to keep this file verbatim or to overload the affected recipes. The section "Moving to the Yocto Project 1.6 Release" in the Yocto manual suggests removing the LICENSE file where possible. Remove LICENSE in cases where COPYING.MIT is also given and replace LICENSE with COPYING.MIT if the former was the only entry. All modified recipes specify LICENSE = "MIT" and none of the in-tree files specify a different license either. As the packages do not change (the license files are not contained in them), do not increase PR. Signed-off-by: Olaf Mandel <o.mandel@menlosystems.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Several recipes reference the LICENSE file in their LIC_FILES_CHKSUM
variable as ${COREBASE}/LICENSE. This forces distribution providers to
keep this file verbatim or to overload the affected recipes. The section
"Moving to the Yocto Project 1.6 Release" in the Yocto manual suggests
removing the LICENSE file where possible.

Remove LICENSE in cases where COPYING.MIT is also given and replace
LICENSE with COPYING.MIT if the former was the only entry. All modified
recipes specify LICENSE = "MIT" and none of the in-tree files specify a
different license either.

As the packages do not change (the license files are not contained in
them), do not increase PR.

Signed-off-by: Olaf Mandel <o.mandel@menlosystems.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Update after toplevel LICENSE file checksum change 2014-01-02T14:19:45+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2014-01-02T14:19:45+00:00 bbd88aebcabbb19c27a7d752d4a5b8ad9ff9412e Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
useradd-example: add example for setting clear text password 2013-12-14T09:16:32+00:00 Chen Qi Qi.Chen@windriver.com 2013-12-10T09:40:37+00:00 6f47698e1ef8103cade8b954825848bb8986158c Use '-P' option for user3 to set a clear text password. This is supposed to serve as an example of how to set clear text password in recipes. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> 
Use '-P' option for user3 to set a clear text password. This is supposed
to serve as an example of how to set clear text password in recipes.

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
useradd-example: use ${datadir} instead of /usr/share for packaging 2012-08-06T13:19:48+00:00 Javier Martinez Canillas javier@dowhile0.org 2012-08-05T19:48:35+00:00 b93a9dadc9a2754d4e33929bda8dba46dd20b694 It is considered good practice to use the build system provided variables instead of directly specify hardcoded paths. Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
It is considered good practice to use the build system provided
variables instead of directly specify hardcoded paths.

Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
useradd-example.bb: update example documentation comments 2011-11-10T11:35:30+00:00 Scott Garman scott.a.garman@intel.com 2011-11-09T02:42:02+00:00 70aaac37968bf2b35d6a536c3f3f69fe3620255c Clarify that only packages listed in USERADD_PACKAGES will include the user/group creation code. Signed-off-by: Scott Garman <scott.a.garman@intel.com> 
Clarify that only packages listed in USERADD_PACKAGES will
include the user/group creation code.

Signed-off-by: Scott Garman <scott.a.garman@intel.com>
useradd-example: example recipe for using inherit useradd 2011-07-01T15:53:46+00:00 Scott Garman scott.a.garman@intel.com 2011-05-18T17:44:59+00:00 89a89caa555e288314c72594a589dcac081154ad An example recipe for demonstrating/documenting how user and group manipulation is done with 'inherit useradd' Signed-off-by: Scott Garman <scott.a.garman@intel.com> 
An example recipe for demonstrating/documenting how user and
group manipulation is done with 'inherit useradd'

Signed-off-by: Scott Garman <scott.a.garman@intel.com>