linux/poky.git/meta/classes/rootfs_ipk.bbclass, branch 1.2_M2.final

classes/image: implement generic locale package installation

2012-01-03T12:14:26+00:00

Let each package-specific rootfs implementation provide basic functions to query the existence of a package and install a list of packages and then have a generic install function so this logic is in one place. Note: unlike previous versions of this code in OE-Core this uses the IMAGE_LINGUAS variable and not IMAGE_LOCALES - note that IMAGE_LINGUAS was what was used in OE-Classic and it is already used in OE-Core in order to install locale-base-*. This will mean that if IMAGE_LINGUAS is left at the default you will now get more packages installed. If you don't want these language support packages then you should set IMAGE_LINGUAS explicitly. This restores locale installation to the same state as OE-Classic, only we now support all the packaging backends. (From OE-Core rev: c0fc36f8629a6abb9a7b542df8a2857526547a31) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

opkg: Update svn 625 -> 633 and fix preinst issues

2011-12-16T16:05:37+00:00

There is a major issue with opkg images at the moment as preinst functions are not being executed before their dependencies are installed and this is leading to corruption of images containing avahi/dbus in particular. There are various changes in upstream opkg in the last 8 revisions which make changes in this area but sadly these aren't enough to get things working for us. I've updated to the latest svn revision with this patch since it makes sense to pull in those changes first and then supplement them with the attached patches. There is a full description of the patches in the patch headers but in summary they: a) Ensure preinst functions execute with their dependencies installed. This is a pretty invasive change as it changes the package install ordering in general. b) Ensure opkg sets $D, not $PKG_ROOT which we don't use c) Change opkg to allow execution of postinstall functions which fail resulting in execution on the target device as rootfs_ipk.bbclass currently does manually. The remaining changes interface this with the rest of the OE build infrastructure, adding in the option to tell opkg to run the preinst and postinst functions, ensure the correct environment is present for the postinst scripts and removing the now unneeded rootfs_ipk class code which opkg now does itself. [YOCTO #1711] (From OE-Core rev: 2feba313c991170747381c7cf821a45c2cd04632) Signed-off-by: Richard Purdie

rootfs_ipk: implement FEED_DEPLOYDIR_BASE_URI support

2011-12-08T15:24:26+00:00

this feature was present in OE-classic, is documented in OE-core but its implementation is actually missing. The present implementation is directly copied from OE-classic and tested on an arm926 machine. (From OE-Core rev: 63b619fd7a3d0ca55a965f0a5b99f6e9c8584ea4) Signed-off-by: Eric Bénard Signed-off-by: Richard Purdie

classes/buildhistory: add new output history collection class

2011-12-05T16:23:53+00:00

Create a new build output history reporting class, using testlab.bbclass from meta-oe as a base. This records information from images produced by the build process in text files structured suitably for tracking within a git repository, thus enabling monitoring of changes over time. Build history collection can be enabled simply by adding the following to your local.conf: INHERIT += "buildhistory" The output after a build can then be found in BUILDHISTORY_DIR (defaults to TMPDIR/buildhistory). If you set up this directory as a git repository and set BUILDHISTORY_COMMIT to "1" in local.conf, the build history data will be committed on every build. (From OE-Core rev: 14acb530a27a3b088d0bfd56db291f4e72ace8ab) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

Revert "classes/buildhistory: add new output history collection class"

2011-12-01T23:02:12+00:00

This reverts commit 508ff624fea705eb93cf2cc1e0c9c42cb817acf8. RP accidentally pulled the wrong commit in, it was supposed to be a *package*history bbclass change. Signed-off-by: Richard Purdie

classes/buildhistory: add new output history collection class

2011-12-01T16:54:07+00:00

Create a new build output history reporting class, using testlab.bbclass from meta-oe and packagehistory.bbclass as a base. This records information from packages and images output from the build process in text files structured suitably for tracking within a git repository, thus enabling monitoring of changes over time. Build history collection can be enabled simply by adding the following to your local.conf: INHERIT += "buildhistory" The output after a build can then be found in BUILDHISTORY_DIR (defaults to TMPDIR/buildhistory). If you set up this directory as a git repository and set BUILDHISTORY_COMMIT to "1" in local.conf, the build history data will be committed on every build. (From OE-Core rev: 508ff624fea705eb93cf2cc1e0c9c42cb817acf8) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

rootfs_ipk.bbclass: Ensure bad recommendations persist in the status file

2011-11-14T11:15:45+00:00

Currently bad recommendations are added to the status file with status "ok". After a single opkg command, whilst it will ignore the recommendation, the status changes to "installed" even if the recommended package was not installed. Whilst this is likely a glitch in opkg's logic, the correct way to persist the information in the status file is to set the status to "hold" as deinstall packages with that status remain. With this change the bad recommendations persist accross multiple opkg runs and the system behaves as expected. [YOCTO #1758] (From OE-Core rev: 215ff6b2e9676c8c7dd8acfd696151bcd0f1490f) Signed-off-by: Richard Purdie

Convert to use direct access to the data store (instead of bb.data.Var())

2011-11-10T11:51:19+00:00

This is the result of running the following over the metadata: sed \ -e 's:bb.data.$setVar([^,()]*,[^,()]*$, *$[^ )]*$ *):\2.\1):g' \ -e 's:bb.data.$setVarFlag([^,()]*,[^,()]*,[^,()]*$, *$[^) ]*$ *):\2.\1):g' \ -e 's:bb.data.$getVar([^,()]*$, *$[^(), ]*$ *,$[^)]*$):\2.\1,\3):g' \ -e 's:bb.data.$getVarFlag([^,()]*,[^,()]*$, *$[^(), ]*$ *,$[^)]*$):\2.\1,\3):g' \ -e 's:bb.data.$getVarFlag([^,()]*,[^,()]*$, *$[^() ]*$ *):\2.\1):g' \ -e 's:bb.data.$getVar([^,()]*$, *$[^) ]*$ *):\2.\1):g' \ -i `grep -ril bb.data *` (From OE-Core rev: b22831fd63164c4db9c0b72934d7d734a6585251) Signed-off-by: Richard Purdie

multilib: Drop MULTILIB_IMAGE_INSTALL

2011-11-08T14:32:55+00:00

There should just be a single IMAGE_INSTALL variable. If the package backends need this split into different multilib components they should be responsible for doing this, not the user. This commit removes the MULTILIB_IMAGE_INSTALL variable. [YOCTO #1564] (From OE-Core rev: 7736862a74c92fe1afe42e170822be13117575c2) Signed-off-by: Dongxiao Xu Signed-off-by: Richard Purdie

rootfs_ipk bbclass: special-case base-passwd preinst to run first

2011-11-04T15:43:29+00:00

Preinst are run alphabetically which breaks when e.g. avahi-daemon needs /etc/passwd present. (From OE-Core rev: d6793165feb26c51b5f19ad1e6d1a4099878e879) Signed-off-by: Koen Kooi Signed-off-by: Richard Purdie

linux/poky.git/meta/classes/rootfs_ipk.bbclass, branch 1.2_M2.final

classes/image: implement generic locale package installation

opkg: Update svn 625 -> 633 and fix preinst issues

rootfs_ipk: implement FEED_DEPLOYDIR_BASE_URI support

classes/buildhistory: add new output history collection class

Revert "classes/buildhistory: add new output history collection class"

classes/buildhistory: add new output history collection class

rootfs_ipk.bbclass: Ensure bad recommendations persist in the status file

Convert to use direct access to the data store (instead of bb.data.*Var*())

multilib: Drop MULTILIB_IMAGE_INSTALL

rootfs_ipk bbclass: special-case base-passwd preinst to run first

Convert to use direct access to the data store (instead of bb.data.Var())