1. Messages
  2. Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS

Re: Package postinstall dependencies - Introduction of PACKAGE_WRITE_DEPS

Burton, Ross <ross.burton@...>
 


On 19 January 2017 at 16:13, Trevor Woerner <twoerner@...> wrote:
Is there not already a mechanism for generically saying "I need <this> task of
<that> recipe to be completed before my <such-and-such> task can run" of which
DEPENDS and RDEPENDS are simply short-hand notations?

If "yes" (and I understand the discussion correctly) couldn't that be employed
here?

If "no" (and I understand the discussion correctly) wouldn't adding such a
mechanism be a possible solution. The use of which, hopefully, would make it
easier for a user to understand what's going on (without requiring ad-hoc
knowledge of the system)?

Yes, there is.  do_some_task[depends] += "some-recipe:some_other_task".

DEPENDS is just a neat way of setting [depends] on do_configure to the list of recipes in DEPENDS's do_populate_sysroot task.

The problem is that do_package_write doesn't exist: the task is do_package_write_deb ..._ipk and ..._rpm.  Thus the single variable that the classes and recipes write to, and the package classes do:

do_package_write_rpm[depends] += "${PACKAGE_WRITE_DEPS}"

Simples!  :)

IMHO, the current name is fine.  As the dependencies are added to do_package_write, it's the most obvious name.

Ross
Join {openembedded-architecture@lists.openembedded.org to automatically receive all group messages.