[OE-core] [PATCH 2/3] systemd: add volatile-binds to RDEPENDS

[ChenQi]

On 07/28/2014 09:21 PM, Richard Purdie wrote:
> On Mon, 2014-07-28 at 13:34 +0800, Chen Qi wrote:
>> ---
>>   meta/recipes-core/systemd/systemd_213.bb |    1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/meta/recipes-core/systemd/systemd_213.bb b/meta/recipes-core/systemd/systemd_213.bb
>> index 5de7cdc..4fb7ffc 100644
>> --- a/meta/recipes-core/systemd/systemd_213.bb
>> +++ b/meta/recipes-core/systemd/systemd_213.bb
>> @@ -243,6 +243,7 @@ FILES_${PN}-dbg += "${rootlibdir}/.debug ${systemd_unitdir}/.debug ${systemd_uni
>>   FILES_${PN}-dev += "${base_libdir}/security/*.la ${datadir}/dbus-1/interfaces/ ${sysconfdir}/rpm/macros.systemd"
>>   
>>   RDEPENDS_${PN} += "kmod dbus util-linux-mount udev (= ${EXTENDPKGV})"
>> +RDEPENDS_${PN} += "volatile-binds"
>>   
>>   RRECOMMENDS_${PN} += "systemd-serialgetty systemd-compat-units udev-hwdb\
>>                         util-linux-agetty \
> Do we always need/want to include this? Does this have any implications
> for rw systems? I couldn't immediately see how this triggers on a ro
> system...
>
> Cheers,
>
> Richard
>
>
>

Hi Richard,

Take var-lib-volatile.service as an example.
In the service file, we have:

ConditionPathIsReadWrite=!/var/lib


So if /var/lib is rw, the service is not started. On a ro system, 
/var/lib is read-only, and the service is started.


I just realized that I didn't put comments in these patches.
I'll send out a V2.

Best Regards,
Chen Qi