<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 24, 2013 at 2:51 PM, Otavio Salvador <span dir="ltr"><<a href="mailto:otavio@ossystems.com.br" target="_blank">otavio@ossystems.com.br</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":zx" style="overflow:hidden">On Wed, Jul 24, 2013 at 3:54 PM, Chris Larson <<a href="mailto:clarson@kergoth.com">clarson@kergoth.com</a>> wrote:<br>
...<br>
<div class="im">> The standalone systemd-tmpfiles recipe I've created has a fairly small set<br>
> of dependencies: intltool-native, dbus, libcap. Given this, I'd like to<br>
> propose transitioning away from populate-volatiles to systemd-tmpfiles, even<br>
> for non-systemd images. I think that the update-tmpfiles shell script may be<br>
> of use in a transition, but before we even begin discussing a transition<br>
> path, I'd like to request comments on the notion of moving to it at all.<br>
<br>
</div>I think it shouldn't be hard to make an C app or script which could<br>
parse systemd-tmpfiles and use this for non-systemd systems. What do<br>
you think?</div></blockquote></div><br>I considered this too, but systemd-tmpfiles supports quite a lot more than volatiles, for example restoring selinux labels. Maybe that sounds fun to you, but it sounded like more trouble than it was worth to me, given systemd-tmpfiles can be used without systemd :) But yes, it's definitely another option to consider. <br>
-- <br>Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics
</div></div>