openembedded-core.git/meta/classes/rootfs_ipk.bbclass, branch daisy

do_rootfs: Add PACKAGE_FEED_URIS as a vardep

2014-03-07T15:04:35+00:00

A bit uncertain on where to put this, suggestions welcome.
Needed to automatically rebuild do_rootfs when PACKAGE_FEED_URIS
change.

Signed-off-by: David Nyström 
Signed-off-by: David Nyström 
Signed-off-by: Saul Wold

(image|rootfs_ipk).bbclass, rootfs.py: ipk multilib fixes

2014-02-13T11:41:16+00:00

This commit whitelists some common directories, so the multilib sanity
checks pass and also fixes an issue in lib/oe/rootfs.py when the
compared files do not exist.

Signed-off-by: Laurentiu Palcu 
Signed-off-by: Richard Purdie

rootfs.py, package_manager.py, sdk.py: Fix building from feeds feature for opkg

2014-02-11T11:50:32+00:00

When using opkg as the PM backend, one has the option to provide custom
feeds to create the rootfs from.

This commit:
 * fixes this in the refactored code;
 * moves the custom config creation code to python;
 * clean up the package-ipk.bbclass;

Signed-off-by: Laurentiu Palcu

Cleanup image,rootfs_ipk,package_ipk bbclass files

2014-02-11T11:50:26+00:00

This commit cleans up the functions that were ported to python.

Signed-off-by: Laurentiu Palcu

rootfs_ipk: Ensure that BAD_RECOMMENDATIONS are honoured for all architectures

2014-02-02T22:37:24+00:00

Commit a5362de60c0051f16b88a40bd9cb41915bee0b0f restricted us to writing
only a single entry to the status file for any given package.  This
avoids writing garbage entries (with no Status) when multiple versions
of the same package exist in the feed.  However, in the case where the
same version exists for multiple architectures (for example, has been
built for both cortexa15 and generic armv7a), we do need to write out
status file entries for all of them since we can't trivially determine
which one opkg will decide to install.

Fix this by undoing a5362de60c0051f16b88a40bd9cb41915bee0b0f and writing
out an entry for everything that matches, but ensuring that we force the
Status to the correct value for each one.

Signed-off-by: Phil Blundell 
Signed-off-by: Richard Purdie

classes/image: write image manifest

2013-11-26T23:00:27+00:00

Write a list of installed packages to a .manifest file next to the
image, so we can find out what went into the image after it has been
constructed without necessarily having to have buildhistory enabled
(although that will provide more detail.) We can make use of this for
example in the testimage class associated code that checks for installed
packages for determining whether or not to run specific tests.

Note: this replaces the previous ipk-specific manifest code with
something that works for ipk, rpm and deb, and instead of a pruned
status file, packages are listed one per line, in the following format:

  

Tests for all three backends have shown that the performance impact of
this change is negligible (about 1.5s max).

Implements [YOCTO #5410]

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

rootfs_*.bbclass: List which post-install scripts can not be run

2013-11-22T13:44:33+00:00

When preping a read-only rootfs and finding some post-install
scripts that can not be run, list the names of said scripts to
avoid having to look around the rootfs to find a list.

Signed-off-by: Jeffrey C Honig 
Signed-off-by: Jeff Polk 
Signed-off-by: Richard Purdie

run-postinst: Ensure that the postinsts are ordered

2013-10-06T08:43:35+00:00

The postinst files were being generated using purely the name of the package,
this unfortunately meant the run order would be based on the name of the
package and not the order in which it was installed on the filesystem.

If package A requires package Z to be fully installed, this causes a problem.

Note:

rpm - as the rpm based install proceeds the order is defined and captured.
      so the problem is resolved there.

ipk - this unfortunately does not appear to solve the problem for ipk, as
      the status file is not ordered in any appreciable way.  This does not
      cause any regressions however and sets the stage for a proper fix.

deb - this -may- fix the deb install.  Early testing indicates at least some
      ordering to the status file.  But it's unclear if it completely resolves
      the issue.

Signed-off-by: Mark Hatle 
Signed-off-by: Saul Wold 
Signed-off-by: Richard Purdie

classes: Remove references to _remove in function names since this may become a bitbake keyword

2013-08-26T10:25:59+00:00

There is a good chance we might want to support a bitbake operator
"_remove" which works in a similar way to _append and _prepend. As
such, we can't use those keywords in function or variable names.

Signed-off-by: Richard Purdie 
Signed-off-by: Saul Wold

classes/rootfs_rpm: implement BAD_RECOMMENDATIONS for RPM

2013-07-28T06:28:29+00:00

Add support for the BAD_RECOMMENDATIONS variable that can be used to
prevent specific packages from being installed via an RRECOMMENDS
relationship when using the RPM backend. (Previously this
functionality was only available when using ipk packaging.)

In the process this moves the defaulting of BAD_RECOMMENDATIONS (as
empty) to bitbake.conf since it is no longer specific to the ipk
backend, as well as unifying some of the code that creates the
configuration for smart for use on the host and target.

Fixes [YOCTO #3916].

Signed-off-by: Paul Eggleton 
Signed-off-by: Saul Wold