Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Dengke Du <dengke.du@windriver.com>,
	OE-core <openembedded-core@lists.openembedded.org>,
	"Burton, Ross" <ross.burton@intel.com>
Subject: Re: avahi 0.7 : should we need to package /run directory or delete it?
Date: Mon, 30 Oct 2017 11:48:31 +0200	[thread overview]
Message-ID: <e992f702-05a4-c745-be37-9514529dc93f@linux.intel.com> (raw)
In-Reply-To: <605ca23e-8fc8-1b36-1e52-d3489d07d1a1@windriver.com>

On 10/30/2017 11:39 AM, Dengke Du wrote:
> Sorry, nothing placed in /run in 0.7 version now, but it replace the 
> directory /var/run,
> 
> there are some difference between /run and /var/run, we can reference:
> 
> https://lists.archlinux.org/pipermail/arch-projects/2011-March/000517.html
> 
> I just doubt can we remove /run directly like we remove /var/run in 
> 0.6.32 version

Why do you doubt that? Check if /run is provided by some base package (I 
honestly don't remember), and if it is, you can simply delete it in 
avahi recipe do_install().

Also, don't forget to fix:
USERADD_PARAM_avahi-daemon = "--system --home /var/run/avahi-daemon \
etc.

What I am getting at is that if you are uncertain about your updates, 
don't just send off the patch to the list. Make an image, boot it, and 
verify that avahi is running, and all the directories look sane.

Alex


      reply	other threads:[~2017-10-30  9:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30  7:21 avahi 0.7 : should we need to package /run directory or delete it? Dengke Du
2017-10-30  9:02 ` Alexander Kanavin
2017-10-30  9:39   ` Dengke Du
2017-10-30  9:48     ` Alexander Kanavin [this message]

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=e992f702-05a4-c745-be37-9514529dc93f@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=dengke.du@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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