From: ChenQi <Qi.Chen@windriver.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Zhenfeng.Zhao@windriver.com,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V7 6/6] volatile-conf-sato: add recipe
Date: Wed, 16 Jan 2013 10:03:18 +0800 [thread overview]
Message-ID: <50F60A66.60504@windriver.com> (raw)
In-Reply-To: <CAP9ODKq6X6o0yRLRUuSFsAPpfqc-9uA7AbtBMyi4qrZgvcFgsA@mail.gmail.com>
On 01/15/2013 07:26 PM, Otavio Salvador wrote:
> On Tue, Jan 15, 2013 at 12:15 AM, <Qi.Chen@windriver.com> wrote:
>> From: Chen Qi <Qi.Chen@windriver.com>
>>
>> This recipe provides a config file for core-image-sato.
>> The config file is used to handle volatile storage in case of a
>> read-only-rootfs image.
>>
>> Also, let core-image-sato.bb depend on this recipe.
>>
>> [YOCTO #3406]
>>
>> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
>> ---
>> meta/recipes-sato/images/core-image-sato.bb | 3 +++
>> .../files/volatiles-readonly-sato | 14 ++++++++++++++
>> .../volatile-conf-sato_1.0.bb | 15 +++++++++++++++
>> 3 files changed, 32 insertions(+)
>> create mode 100644 meta/recipes-sato/readonly-volatile-conf/files/volatiles-readonly-sato
>> create mode 100644 meta/recipes-sato/readonly-volatile-conf/volatile-conf-sato_1.0.bb
> Please name the package and the dir the same. It will be confusing for
> user to try to guess where the .bb file is otherwise.
Hi Otavio,
As the conf file is related to the image recipe, so I keep the same
directory hierarchy with the image recipes. Thus, instead of creating
distinct directories for each conf recipe, I gather them together, in
the way image recipes are organized.
poky/meta/recipes-core/images/
-- image recipe 1
-- image recipe 2
poky/meta/recipes-sato/images/
-- image recipe 1
-- image recipe 2
poky/meta/recipes-core/readonly-volatile-conf/
-- conf recipe 1
-- conf recipe 2
poky/meta/recipes-sato/readonly-volatile-conf/
-- conf recipe 1
-- conf recipe 2
Cheers,
Chen Qi
>> diff --git a/meta/recipes-sato/images/core-image-sato.bb b/meta/recipes-sato/images/core-image-sato.bb
>> index f52a1a5..a3d3d27 100644
>> --- a/meta/recipes-sato/images/core-image-sato.bb
>> +++ b/meta/recipes-sato/images/core-image-sato.bb
>> @@ -6,6 +6,9 @@ IMAGE_FEATURES += "splash package-management x11-base x11-sato ssh-server-dropbe
>>
>> LICENSE = "MIT"
>>
>> +RDEPENDS += "volatile-conf-sato"
>> +
>> inherit core-image
>>
>> IMAGE_INSTALL += "packagegroup-core-x11-sato-games"
>> +IMAGE_INSTALL += "volatile-conf-sato"
>> diff --git a/meta/recipes-sato/readonly-volatile-conf/files/volatiles-readonly-sato b/meta/recipes-sato/readonly-volatile-conf/files/volatiles-readonly-sato
>> new file mode 100644
>> index 0000000..4a56b81
>> --- /dev/null
>> +++ b/meta/recipes-sato/readonly-volatile-conf/files/volatiles-readonly-sato
>> @@ -0,0 +1,14 @@
>> +# This configuration file lists filesystem objects specific to sato image
>> +# with read-only rootfs.
>> +# This configuration file will only be applied if the image is sato and the
>> +# rootfs is read-only.
>> +# For the detailed format information, refer to /etc/default/volatiles/00_core.
>> +d root root 0755 /var/volatile/lib/ none
>> +d root root 0755 /var/volatile/lib/urandom/ none
>> +d root root 0755 /var/volatile/lib/dropbear/ none
>> +d root root 0755 /var/volatile/lib/nfs/ none
>> +d root root 0755 /var/volatile/lib/dbus/ none
>> +l root root 0755 /var/lib/urandom /var/volatile/lib/urandom
>> +l root root 0755 /var/lib/dropbear /var/volatile/lib/dropbear
>> +l root root 0755 /var/lib/nfs /var/volatile/lib/nfs
>> +l root root 0755 /var/lib/dbus /var/volatile/lib/dbus
>> diff --git a/meta/recipes-sato/readonly-volatile-conf/volatile-conf-sato_1.0.bb b/meta/recipes-sato/readonly-volatile-conf/volatile-conf-sato_1.0.bb
>> new file mode 100644
>> index 0000000..acc8901
>> --- /dev/null
>> +++ b/meta/recipes-sato/readonly-volatile-conf/volatile-conf-sato_1.0.bb
>> @@ -0,0 +1,15 @@
>> +SUMMARY = "Provide config files for core-image-sato"
>> +DESCRIPTION = "This package contains a config file for core-image-sato. \
>> +It is used to handle volatile storage in case of a read-only rootfs."
>> +
>> +LICENSE = "MIT"
>> +LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
>> +
>> +SRC_URI = "file://volatiles-readonly-sato"
>> +
>> +PR = "r1"
>> +
>> +do_install () {
>> + install -d ${D}${sysconfdir}/default/volatiles
>> + install -m 0644 ${WORKDIR}/volatiles-readonly-sato ${D}${sysconfdir}/default/volatiles/00_core_readonly
>> +}
>> --
>> 1.7.9.5
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
> --
> Otavio Salvador O.S. Systems
> E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
> Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
>
>
next prev parent reply other threads:[~2013-01-16 2:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 2:15 [PATCH V7 6/6] volatile-conf-sato: add recipe Qi.Chen
2013-01-15 11:26 ` Otavio Salvador
2013-01-16 2:03 ` ChenQi [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-14 8:35 [PATCH V7 0/6] read-only rootfs support Qi.Chen
2013-01-14 8:35 ` [PATCH V7 6/6] volatile-conf-sato: add recipe Qi.Chen
2013-01-15 2:11 ` ChenQi
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=50F60A66.60504@windriver.com \
--to=qi.chen@windriver.com \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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