* avahi 0.7 : should we need to package /run directory or delete it?
@ 2017-10-30 7:21 Dengke Du
2017-10-30 9:02 ` Alexander Kanavin
0 siblings, 1 reply; 4+ messages in thread
From: Dengke Du @ 2017-10-30 7:21 UTC (permalink / raw)
To: OE-core, Burton, Ross
Hi Ross
The new version of avahi 0.7 use /run directory to place some run-time
variable data,
not /var/run, should we need to package it or delete it?
Thanks!
Dengke
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: avahi 0.7 : should we need to package /run directory or delete it?
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
0 siblings, 1 reply; 4+ messages in thread
From: Alexander Kanavin @ 2017-10-30 9:02 UTC (permalink / raw)
To: Dengke Du, OE-core, Burton, Ross
On 10/30/2017 09:21 AM, Dengke Du wrote:
> The new version of avahi 0.7 use /run directory to place some run-time
> variable data,
>
> not /var/run, should we need to package it or delete it?
Can you provide details please? What is being placed there and at which
point?
Alex
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: avahi 0.7 : should we need to package /run directory or delete it?
2017-10-30 9:02 ` Alexander Kanavin
@ 2017-10-30 9:39 ` Dengke Du
2017-10-30 9:48 ` Alexander Kanavin
0 siblings, 1 reply; 4+ messages in thread
From: Dengke Du @ 2017-10-30 9:39 UTC (permalink / raw)
To: Alexander Kanavin, OE-core, Burton, Ross
Hi Alex
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
bbfile.
In 0.6.32 Makefile of avahi:
avahi_runtime_dir = /var/run
avahi_socket = /var/run/avahi-daemon/socket
In 0.7 Makefile of avahi:
avahi_runtime_dir = /run
avahi_socket = /run/avahi-daemon/socket
On 2017年10月30日 17:02, Alexander Kanavin wrote:
> On 10/30/2017 09:21 AM, Dengke Du wrote:
>
>> The new version of avahi 0.7 use /run directory to place some
>> run-time variable data,
>>
>> not /var/run, should we need to package it or delete it?
>
> Can you provide details please? What is being placed there and at
> which point?
>
> Alex
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: avahi 0.7 : should we need to package /run directory or delete it?
2017-10-30 9:39 ` Dengke Du
@ 2017-10-30 9:48 ` Alexander Kanavin
0 siblings, 0 replies; 4+ messages in thread
From: Alexander Kanavin @ 2017-10-30 9:48 UTC (permalink / raw)
To: Dengke Du, OE-core, Burton, Ross
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-10-30 9:48 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox