From: Piotr Piwko <piotr.piwko@gmail.com>
To: Qi.Chen@windriver.com
Cc: yocto@yoctoproject.org
Subject: Re: Check IMAGE_FEATURES content in recipe
Date: Thu, 10 May 2018 08:59:44 +0000 [thread overview]
Message-ID: <CAMTWR-Np4pd8tytDdOoabzEZsqU=2w95Y9ddh6UOsD4-F4eDCw@mail.gmail.com> (raw)
In-Reply-To: <d2ed93c9-f746-6e37-c959-66a5eebfb93d@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
czw., 10 maj 2018 o 10:45 ChenQi <Qi.Chen@windriver.com> napisał(a):
> Hi Piotr,
>
> VAR set in recipe A cannot be accessed by recipe B.
>
All right, but what about DISTRO_FEATURES? It is available everywhere, so
maybe there is some possibility to do so ...
> For 'read-only-rootfs' image feature, tweaks are done in functions
> executed after generating rootfs.
> meta/classes/rootfs-postcommands.bbclass:ROOTFS_POSTPROCESS_COMMAND +=
> '${@bb.utils.contains("IMAGE_FEATURES", "read-only-rootfs",
> "read_only_rootfs_hook; ", "",d)}'
>
> Can you use a similar approach to solve your problem?
>
Unfortunately, I can not. I would like to make a pkg_postinst() function of
my package dependent on the rootfs mount mode. It should be different if
the rootfs is going to be mounted as read-only.
--
Piotr Piwko
http://www.embedded-engineering.pl/
[-- Attachment #2: Type: text/html, Size: 1774 bytes --]
next prev parent reply other threads:[~2018-05-10 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 7:37 Check IMAGE_FEATURES content in recipe Piotr Piwko
2018-05-10 8:46 ` ChenQi
2018-05-10 8:54 ` André Draszik
2018-05-10 8:59 ` Piotr Piwko [this message]
2018-05-10 9:22 ` Burton, Ross
2018-05-10 15:06 ` Marcelo E. Magallon
2018-05-11 0:04 ` Paul Eggleton
2018-05-10 10:54 ` Alexander Kanavin
2018-05-10 11:29 ` Piotr Piwko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMTWR-Np4pd8tytDdOoabzEZsqU=2w95Y9ddh6UOsD4-F4eDCw@mail.gmail.com' \
--to=piotr.piwko@gmail.com \
--cc=Qi.Chen@windriver.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.