linux/poky.git/meta/classes/package_rpm.bbclass, branch 1.1_M2

classes/package_rpm.bbclass: Change the way the PV is transformed

2011-06-23T15:02:40+00:00

There were some odd instances where the PKGV could not be loaded in the old way. Change to verify that PKGV exists before attempting to retrieve the value from the key. (From OE-Core rev: c2ce3573fb2816cd2023a56b364fae4c0f4455ae) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

classes/package_rpm.bbclass: Enhance diagnostic messages

2011-06-23T11:07:36+00:00

We clearly state now if we are: * Skipping an empty package * Creating a (full) package * Creating an empty package (From OE-Core rev: 3db9d865ef7d65e3712eb7f9a659bb31cb3cb75e) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

package_rpm.bbclass: make RPM use on-disk permissions

2011-06-06T14:58:42+00:00

Instruct RPM to use the on-disk permissions, owners, groups, and directory permissions, instead of defaulting to root:root Code changes suggested by Mark Hatle. (From OE-Core rev: a6464f9484f56f596e3215184ad56ac6769ebb0c) Signed-off-by: Scott Garman Signed-off-by: Richard Purdie

classes/package_xxx.class: Use PKGE/PKGV/PKGR.

2011-05-27T16:55:49+00:00

Use PKGE/PKGV/PKGR to build various package feed in tasks of pacakge_write_xxx. (From OE-Core rev: c2872315905fcdf6e4bf11fe96e5ca62af3475f8) Signed-off-by: Lianhao Lu Signed-off-by: Richard Purdie

Move packagedata code into oe.packagedata (sync from OE)

2011-05-20T18:07:51+00:00

(From OE-Core rev: e6858627ab087f2f25ebbd6c4422eeae35f3b0ac) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

package-index.bb: add support for deb and rpm.

2011-05-20T11:40:44+00:00

[YOCTO #1024] Currently package-index.bb only supports ipk. This commit adds the support for rpm and deb, too. ------------------------------ How to generate and use repos: 1) run "bitbake package-index" after building some target, e.g., core-image-sato-sdk; 2) export ${DEPLOY_DIR_RPM}, ${DEPLOY_DIR_IPK} and ${DEPLOY_DIR_DEB} by a webserver on the host, assuming the host IP is 192.168.7.1, at http://192.168.7.1/rpm http://192.168.7.1/ipk http://192.168.7.1/deb 3) inside the target, according to the packaging system (rpm, ipk or deb) used when we generate the target image, we can use different ways to manage packages: 3.1) RPM run "zypper addrepo http://192.168.7.1/rpm main; zypper refresh" to retrieve info about the repo; next, we can use "zypper install/remove" to manage packages. 3.2) IPK add the repo info into opkg config file, i.e., in /etc/opkg/arch.conf, we can add something like "src i586 http://192.168.7.1/ipk/i586", and next, we run "opkg update" to make opkg update the list of available packages. And later, we can use "opkg install/remove" to manage packages. 3.3) DEB Currently in target, some important config files, like /var/lib/dpkg/status and /etc/apt/sources.list, for deb/apt are missing. So we can't install/remove package in target at present. (From OE-Core rev: 01e34bdb43e0cc27c1cfffd6730c384f40c404c1) Signed-off-by: Dexuan Cui Signed-off-by: Richard Purdie

package_rpm: use target vendor information

2011-05-10T08:56:20+00:00

* Instead of hardcoding target vendor string "-poky" use TARGET_VENDOR information in case of using external toolchains (From OE-Core rev: 0638c470410b7ac3057d8f64ae0d389b5c3da838) Signed-off-by: Adrian Alonso Signed-off-by: Richard Purdie

package_rpm: Ensure we take the sstate shared lockfile in the place we write files

2011-03-29T13:01:52+00:00

The point we need to take the lock is when the rpm files are written into the deploy rpm directory. Since sstate makes the actual installation of the files, that is the point we need to take the lock. This also stops the deploy/rpm directory being accessed for a lock before it exists. [YOCTO #797] [YOCTO #925] (From OE-Core rev: 833a1e970f087dfcb32967cee3e24540f041cde0) Signed-off-by: Richard Purdie

package_rpm: Fix rootfs generation

2011-03-11T02:46:02+00:00

[YOCTO #797] During rootfs generation, if other RPM packages are being wrtten this could cause a failure during the solvedb generation. We add a shared lock around the RPM package building. This will allow multiple RPM packages to continue to be written at the same time, but prevent rootfs generation and RPM package generation at the same time. (From OE-Core rev: 1d5ca654a482f582c75faf546140dfd6064da73b) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

rootfs_rpm: Fix rootfs generation using RPM packages

2011-02-25T23:31:50+00:00

[BUG #756] Fix bug #756. The rootfs contains a control file /etc/rpm/platform that specifies the default system platform, as well as patterns for compatible architectures. This file was not being setup properly due to a misunderstanding of the format in a previous patch. Signed-off-by: Mark Hatle