All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] dnsmasq: merge dnsmasq-dbus to main recipe
Date: Sun, 14 Apr 2013 16:09:21 +0100	[thread overview]
Message-ID: <9692220.xQMF5DQqQm@helios> (raw)
In-Reply-To: <20130414150423.GF2475@jama>

On Sunday 14 April 2013 17:04:23 Martin Jansa wrote:
> On Sun, Apr 14, 2013 at 04:01:59PM +0100, Paul Eggleton wrote:
> > On Sunday 14 April 2013 15:49:34 Martin Jansa wrote:
> > > * they conflict in sysroot anyway, should be converted to PACKAGECONFIG
> > > 
> > >   but because dbus is already built in most images I'll let it for
> > >   someone
> > >   who has such use-case
> > 
> > Hang on a sec, I agree it's good to get rid of this second recipe, but
> > you're changing the default - so at least give people a way to influence
> > it. It's not too hard to put in PACKAGECONFIG now while you're changing
> > the recipe anyway.
>
> is there someone who needs dnsmasq without dbus?

It's not too hard to imagine a minimal system that wants one and not the 
other. We had two recipes originally for a reason. Sure, it's fine if you're 
already using something that uses dbus and therefore you'll have it anyway, 
but not everyone is in the same situation.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2013-04-14 15:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14 13:49 [meta-oe][PATCH] dnsmasq: merge dnsmasq-dbus to main recipe Martin Jansa
2013-04-14 15:01 ` Paul Eggleton
2013-04-14 15:04   ` Martin Jansa
2013-04-14 15:09     ` Paul Eggleton [this message]
2013-04-15 17:13       ` Paul Eggleton

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=9692220.xQMF5DQqQm@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=martin.jansa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.