Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Jonathan Liu <net147@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Fix guide for unshipped files in run directory
Date: Thu, 13 Jun 2013 00:12:28 +1000	[thread overview]
Message-ID: <51B881CC.4050303@gmail.com> (raw)

Hi,

After 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ea647cd9eebdc3e3121b84074519c4bb305adac9, 
some recipes that previously installed /var/run or files inside /var/run 
may now show QA warnings. The following is a rough guide on how to fix them.

Fix guide for unshipped files in run directory:

- If package just installs empty run directory, remove it by adding
the following to do_install_append():
rmdir "${D}${localstatedir}/run"
rmdir --ignore-fail-on-non-empty "${D}${localstatedir}"
Reference: 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2aa350acca1c6b6ada6a4508611ce25e9f9576ab

- If the package creates folders inside the run directory, stop the
service, rename to something else and try starting it again. If the
service recreates the folders with the same permissions and still
starts correctly, these folders can be removed in do_install_append()
with:
rm -fr "${D}${localstatedir}/run"
Reference: 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=aa6408b05c5eb17b6e9fc280069f3b15eafbdab0

- If the package actually requires folders inside run directory to
start up properly and doesn't create them automatically, a file
listing them needs to be added to tmpfiles.d (for systemd) and
volatiles (for sysvinit).
Reference: 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=9623ccf70221f81861a42cac1eb372d77ea40ba9

Regards,
Jonathan


                 reply	other threads:[~2013-06-12 14:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=51B881CC.4050303@gmail.com \
    --to=net147@gmail.com \
    --cc=openembedded-devel@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