Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: Guo Chunrong-B40290 <B40290@freescale.com>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>,
	Yu Zongchun-B40527 <B40527@freescale.com>
Subject: Re: [meta-networking][PATCH] dnsmasq: install .service only with systemd in DISTRO_FEATURES
Date: Tue, 9 Jul 2013 14:58:03 -0400	[thread overview]
Message-ID: <20130709185803.GA13741@windriver.com> (raw)
In-Reply-To: <B21730BB6DA1D24B83348D9301EA417E1040BD1A@039-SN2MPN1-021.039d.mgd.msft.net>

[-- Attachment #1: Type: text/plain, Size: 3905 bytes --]

[RE: [oe] [meta-networking][PATCH] dnsmasq: install .service only with systemd in DISTRO_FEATURES] On 13.07.05 (Fri 07:45) Guo Chunrong-B40290 wrote:

> Hello, Joe MacDonald
> New  patch was submitted.
> I do not modify (atftp/tracker/gateone)  recips and slim recipes do not work.
> SO the code in these recipes  add  ${systemd_unitdir} to FILES and these recipes work well. 

Just FYI, I saw your patch, I have it in a merge queue, but right now
I'm looking at the bug Paul quoted and the mailing list discussion
quoted therein to see if we can come up with a better, more general
solution.

-J.

> 
> Thanks,
> chunrong
> 
> -----Original Message-----
> From: Joe MacDonald [mailto:Joe.MacDonald@windriver.com] 
> Sent: Thursday, July 04, 2013 7:18 PM
> To: openembedded-devel@lists.openembedded.org
> Cc: Guo Chunrong-B40290; Yu Zongchun-B40527
> Subject: Re: [oe] [meta-networking][PATCH] dnsmasq: install .service only with systemd in DISTRO_FEATURES
> 
> [Re: [oe] [meta-networking][PATCH] dnsmasq: install .service only with systemd in DISTRO_FEATURES] On 13.07.04 (Thu 11:50) Paul Eggleton wrote:
> 
> > On Thursday 04 July 2013 17:26:23 Chunrong Guo wrote:
> > > Signed-off-by: Chunrong Guo <B40290@freescale.com>
> > > ---
> > >  .../recipes-support/dnsmasq/dnsmasq.inc            |    8 +++++---
> > >  1 files changed, 5 insertions(+), 3 deletions(-)
> > > 
> > > diff --git a/meta-networking/recipes-support/dnsmasq/dnsmasq.inc
> > > b/meta-networking/recipes-support/dnsmasq/dnsmasq.inc index
> > > 0f5b273..0710893 100644
> > > --- a/meta-networking/recipes-support/dnsmasq/dnsmasq.inc
> > > +++ b/meta-networking/recipes-support/dnsmasq/dnsmasq.inc
> > > @@ -30,9 +30,11 @@ do_install () {
> > >      install -d ${D}${sysconfdir}/ ${D}${sysconfdir}/init.d 
> > > ${D}${sysconfdir}/dnsmasq.d install -m 644 ${WORKDIR}/dnsmasq.conf 
> > > ${D}${sysconfdir}/
> > >      install -m 755 ${WORKDIR}/init ${D}${sysconfdir}/init.d/dnsmasq
> > > -
> > > -    install -d ${D}${systemd_unitdir}/system
> > > -    install -m 0644 ${WORKDIR}/dnsmasq.service
> > > ${D}${systemd_unitdir}/system +
> > > +    if 
> > > + ${@base_contains('DISTRO_FEATURES','systemd','true','false',d)};
> > > then +        install -d ${D}${systemd_unitdir}/system
> > > +        install -m 0644 ${WORKDIR}/dnsmasq.service
> > > ${D}${systemd_unitdir}/system +    fi
> > > 
> > >      if [ "${@base_contains('PACKAGECONFIG', 'dbus', 'dbus', '', d)}" != ""
> > > ]; then install -d ${D}${sysconfdir}/dbus-1/system.d
> > 
> > I think we should really have a global fix for this issue rather than 
> > hacking up every recipe:
> > 
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=4309
> 
> I'm inclined to agree, but looking at the bug it looks like the potential solution was discussed in February and it's on the schedule for Yocto 1.5, but that's October.
> 
> So I did a quick survey, here's the meta-networking recipes that'll be impacted, if we adopt the workaround approach:
> 
>    - net-snmp
>    - dnsmasq (obviously)
>    - ypbind-mt
>    - yp-tools
>    - ntp
>    - atftp
> 
> I decided I'd have a look at meta-oe for contrast (and guidance) and this is what I found there:
> 
>    - slim
>    - tracker
>    - cloud9
>    - zram
>    - gpsd
>    - gateone
> 
> On the other hand, xinput-calibrator and xserver-nodm-init,  already have the same fix in it Chunrong is proposing.  So the impact of doing either isn't huge, but it's not small either.
> 
> Chunrong:  Would you be willing to retest and resubmit your patch with the above listed meta-networking recipes as a set?  I don't see a lot of sense in doing this piecemeal, I'm okay with taking a workaround until
> #4309 gets fixed, but I'd rather tear the band-aid off all at once, so to speak.
> 
> --
> -Joe MacDonald.
> :wq
> 

-- 
-Joe MacDonald.
:wq

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-07-09 18:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04  9:26 [meta-networking][PATCH] dnsmasq: install .service only with systemd in DISTRO_FEATURES Chunrong Guo
2013-07-04 10:50 ` Paul Eggleton
2013-07-04 11:18   ` Joe MacDonald
2013-07-04 12:47     ` Paul Eggleton
2013-07-04 13:02       ` Joe MacDonald
2013-07-05  7:45     ` Guo Chunrong-B40290
2013-07-09 18:58       ` Joe MacDonald [this message]
2013-07-09 20:43         ` Martin Jansa

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=20130709185803.GA13741@windriver.com \
    --to=joe.macdonald@windriver.com \
    --cc=B40290@freescale.com \
    --cc=B40527@freescale.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