public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Qi.Chen@windriver.com
Cc: Zhenfeng.Zhao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 05/12] volatiles.bbclass: add recipe
Date: Thu, 24 Jan 2013 11:31:50 +0100	[thread overview]
Message-ID: <20130124103150.GA3012@jama> (raw)
In-Reply-To: <c60b41bd635d38aa01ffdd5c6221fd1a9c34b68f.1359014474.git.Qi.Chen@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]

On Thu, Jan 24, 2013 at 04:16:45PM +0800, Qi.Chen@windriver.com wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
> 
> All recipes that need to tweak their directories need to inherit this
> class and set VOLATILE_DIR, VOLATILE_LINK and VOLATILE_PKGS.
> 
> [YOCTO #3406]
> 
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
>  meta/classes/volatiles.bbclass |   11 +++++++++++
>  1 file changed, 11 insertions(+)
>  create mode 100644 meta/classes/volatiles.bbclass
> 
> diff --git a/meta/classes/volatiles.bbclass b/meta/classes/volatiles.bbclass
> new file mode 100644
> index 0000000..f27e598
> --- /dev/null
> +++ b/meta/classes/volatiles.bbclass
> @@ -0,0 +1,11 @@
> +# This bbclass is for read-only-rootfs support. All recipes that may tweak their
> +# own directories in order to run correctly in a read-only rootfs enviroment
> +# should inherit this class and set VOLATILE_DIR, VOLATILE_LINK, VOLATILE_PKGS.
> +
> +# For each package, the net result is a read-only specific conf file generated
> +# and packaged, which has the name of readonly-${VOLATILESPN}.
> +
> +# All these config files are then parsed by populate-volatile.sh to create proper
> +# directories and links.
> +
> +inherit ${@base_contains('DISTRO_FEATURES','sysvinit','volatiles_sysvinit','',d)}

Does "inherit " work?

I mean empty inherit when DISTRO_FEATURES don't contain sysvinit? IIRC
it will fail to parse.

Cheers,

> -- 
> 1.7.9.5
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-01-24 10:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24  8:16 [PATCH 00/12] read-only rootfs support Qi.Chen
2013-01-24  8:16 ` [PATCH 01/12] sysvinit: add ROOTFS_READ_ONLY variable to rcS-default Qi.Chen
2013-01-24  8:16 ` [PATCH 02/12] image.bbclass: add a hook funtion to support readonly rootfs Qi.Chen
2013-01-24 19:44   ` Mark Hatle
2013-01-25  2:49     ` ChenQi
2013-01-24  8:16 ` [PATCH 03/12] core-image.bbclass: support read-only rootfs Qi.Chen
2013-01-24  8:16 ` [PATCH 04/12] package.bbclass: add VOLATILE_DIR and VOLATILE_LINK to PACKAGEVARS Qi.Chen
2013-01-24  8:16 ` [PATCH 05/12] volatiles.bbclass: add recipe Qi.Chen
2013-01-24 10:31   ` Martin Jansa [this message]
2013-01-24 11:37     ` Richard Purdie
2013-01-24 11:45       ` Burton, Ross
2013-01-25  8:58         ` ChenQi
2013-01-25 14:05           ` Burton, Ross
2013-01-28  3:32             ` ChenQi
2013-01-24  8:16 ` [PATCH 06/12] volatiles_sysvinit.bbclass: " Qi.Chen
2013-01-24  8:16 ` [PATCH 07/12] populate-volatile.sh: improve this script Qi.Chen
2013-01-24  8:16 ` [PATCH 08/12] initscripts: let populate-volatile.sh create the /tmp link Qi.Chen
2013-01-24 16:11   ` Mark Hatle
2013-01-24 17:39   ` Mark Hatle
2013-01-25  6:17     ` ChenQi
2013-01-24  8:16 ` [PATCH 09/12] initscripts: inherit volatiles to support read-only rootfs Qi.Chen
2013-01-25 13:11   ` Burton, Ross
2013-01-25 14:14     ` Richard Purdie
2013-01-28  2:11       ` ChenQi
2013-01-28  1:45     ` ChenQi
2013-01-24  8:16 ` [PATCH 10/12] dropbear: " Qi.Chen
2013-01-24  8:16 ` [PATCH 11/12] nfs-utils: " Qi.Chen
2013-01-24  8:16 ` [PATCH 12/12] dbus: " Qi.Chen
2013-01-24 10:45   ` Burton, Ross
2013-01-25  3:05     ` ChenQi
2013-01-25 13:02       ` Burton, Ross

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=20130124103150.GA3012@jama \
    --to=martin.jansa@gmail.com \
    --cc=Qi.Chen@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox