generic-poky

OpenEmbedded "poky" with some sysmocom specific modifications. Mostly used only up to sysmocom release 201310, but the "pyro" branch is still used for 201705

Go to file

André Draszik 7ca04fef1b useradd-staticids: don't create username-group if gid is specified Adding distcc to an image, and having staticids enabled, doesn't work as it causes a a superfluous 'distcc' group being added using a conflicting GID, thus failing the build: \| ERROR: distcc-3.2-r0 do_prepare_recipe_sysroot: distcc: groupadd command did not succeed. Compared to other recipes, the distcc recipe only specifies --gid for the primary group, and doesn't specify --no-user-group, but when --gid is given, it doesn't make sense to create a matching username-group in addition, even if --no-user-group was not specified, and 'useradd' actually complains if --gid and --user-group are given both. If only --gid is given, the current code in here effectively behaves as if --user-group was specified, taking the group-id of the username-group from the --gid parameter. This causes the error above, as we try to add a new group (distcc) with an existing group-id (nogroup). This is contrary to the comment in this file just above, contrary to what useradd can do, contrary to behaviour without the useradd-staticids bbclass, and non-intuitive. Change the code such that a username-group is only created - if a primary group using --gid was not specified, or - if --no-user-group was not specified To be in line with useradd, if gid is not given, and --no-user-group is given, we add the user to the group 'users', which mimics useradd's behaviour. (From OE-Core rev: b1843e60ebe534243b49f3685540fa5ea49d5f35) Signed-off-by: André Draszik <adraszik@tycoint.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit fc3a86ae68919cec72c1a8ae0f9ba1f98ae13f0d) Signed-off-by: André Draszik <adraszik@tycoint.com> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2017-11-05 22:39:48 +00:00
bitbake	bitbake: tests/fetch: handle network failures gracefully	2017-11-05 22:37:29 +00:00
documentation	ref-manual: Fixed broken link.	2017-09-02 00:52:57 +01:00
meta	useradd-staticids: don't create username-group if gid is specified	2017-11-05 22:39:48 +00:00
meta-poky	poky: Update version to 2.3.2	2017-09-11 22:16:59 +01:00
meta-selftest	wic-image-minimal: stop using core-image-minimal	2017-04-12 15:09:58 +01:00
meta-skeleton	useradd-example: exclude from world	2017-01-09 13:39:11 +00:00
meta-yocto/conf	meta-yocto: Rename to meta-poky to better match its purpose	2016-02-28 11:31:17 +00:00
meta-yocto-bsp	linux-yocto/4.1: generix86* bsp fix perf issue with gcc >=7	2017-09-21 17:19:25 +01:00
scripts	oe-pkgdata-util: package-info: Allow extra variables to be displayed	2017-11-05 22:39:47 +00:00
.gitignore	add !meta-poky to .gitignore file	2016-03-26 08:06:58 +00:00
.templateconf	meta-yocto: Rename to meta-poky to better match its purpose	2016-02-28 11:31:17 +00:00
LICENSE	Fix license notices for OE-Core	2014-01-02 12:58:54 +00:00
README	meta-yocto: Rename to meta-poky to better match its purpose	2016-02-28 11:31:17 +00:00
README.hardware	README.hardware: update MPC8315E-RDB section	2017-01-16 18:08:20 +00:00
oe-init-build-env	oe-init-build-env*: Make them actually return failures	2016-03-20 23:12:30 +00:00
oe-init-build-env-memres	oe-init-build-env*: Make them actually return failures	2016-03-20 23:12:30 +00:00

README

Poky
====

Poky is an integration of various components to form a complete prepackaged
build system and development environment. It features support for building
customised embedded device style images. There are reference demo images
featuring a X11/Matchbox/GTK themed UI called Sato. The system supports
cross-architecture application development using QEMU emulation and a
standalone toolchain and SDK with IDE integration.

Additional information on the specifics of hardware that Poky supports
is available in README.hardware. Further hardware support can easily be added
in the form of layers which extend the systems capabilities in a modular way.

As an integration layer Poky consists of several upstream projects such as 
BitBake, OpenEmbedded-Core, Yocto documentation and various sources of information 
e.g. for the hardware support. Poky is in turn a component of the Yocto Project.

The Yocto Project has extensive documentation about the system including a 
reference manual which can be found at:
    http://yoctoproject.org/documentation

OpenEmbedded-Core is a layer containing the core metadata for current versions
of OpenEmbedded. It is distro-less (can build a functional image with
DISTRO = "nodistro") and contains only emulated machine support.

For information about OpenEmbedded, see the OpenEmbedded website:
    http://www.openembedded.org/

Where to Send Patches
=====================

As Poky is an integration repository (built using a tool called combo-layer),
patches against the various components should be sent to their respective
upstreams:

bitbake:
    Git repository: http://git.openembedded.org/bitbake/
    Mailing list: bitbake-devel@lists.openembedded.org

documentation:
    Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
    Mailing list: yocto@yoctoproject.org

meta-poky, meta-yocto-bsp:
    Git repository: http://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto(-bsp)
    Mailing list: poky@yoctoproject.org

Everything else should be sent to the OpenEmbedded Core mailing list.  If in
doubt, check the oe-core git repository for the content you intend to modify.
Before sending, be sure the patches apply cleanly to the current oe-core git
repository.

    Git repository: http://git.openembedded.org/openembedded-core/
    Mailing list: openembedded-core@lists.openembedded.org

Note: The scripts directory should be treated with extra care as it is a mix of
oe-core and poky-specific files.