All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/5] Enable VPN support in ConnMan
Date: Mon, 13 May 2013 12:02:48 +0100	[thread overview]
Message-ID: <1368442968.6920.4.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <3529451.hQA8zCVn47@helios>

On Sun, 2013-05-12 at 20:55 +0100, Paul Eggleton wrote:
> That doesn't work well for software layers - it is not a good thing for 
> various recipes to get rebuilt just because you add meta-oe to your 
> configuration for example.
> 
> The protocol we've established is to add PACKAGECONFIG options to enable the 
> dependencies but have them disabled by default; these can be enabled as 
> desired in distro or local configuration when the layer satisfying the 
> dependency is also enabled.

That doesn't seem totally ideal either, since it means that oe-core ends
up containing a bunch of "joke" PACKAGECONFIG options that will break
your build if you enable them (unless you add some other layer at the
same time).  Personally I would have thought that unnecessary rebuilds
of the handful of packages that this would affect were probably the
lesser of the two evils, though obviously it's not my choice to make.

p.





  parent reply	other threads:[~2013-05-13 11:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 12:33 [PATCH 0/5] Enable VPN support in ConnMan Jukka Rissanen
2013-05-10 12:33 ` [PATCH 1/5] connman: Enable VPN support Jukka Rissanen
2013-05-10 12:33 ` [PATCH 2/5] connman: Add OpenVPN support Jukka Rissanen
2013-05-10 12:33 ` [PATCH 3/5] connman: Add vpnc support Jukka Rissanen
2013-05-10 12:33 ` [PATCH 4/5] connman: Add L2TP support Jukka Rissanen
2013-05-10 12:33 ` [PATCH 5/5] connman: Add PPTP support Jukka Rissanen
2013-05-10 13:47 ` [PATCH 0/5] Enable VPN support in ConnMan Burton, Ross
2013-05-10 22:22 ` Saul Wold
2013-05-11 13:59   ` Philip Balister
2013-05-12 13:27     ` Otavio Salvador
2013-05-12 15:40       ` Saul Wold
2013-05-12 16:32         ` Khem Raj
2013-05-12 18:54         ` Phil Blundell
2013-05-12 19:55           ` Paul Eggleton
2013-05-13  8:00             ` Saul Wold
2013-05-13  8:33               ` Paul Eggleton
2013-05-13  8:44                 ` Saul Wold
2013-05-13 11:02             ` Phil Blundell [this message]
2013-05-13 11:06               ` Burton, Ross
2013-05-13 11:16                 ` Phil Blundell
2013-05-13 11:32                 ` Tomas Frydrych
2013-05-13 14:24                   ` Burton, Ross
2013-05-13 14:53                   ` Phil Blundell
2013-05-14  9:22                     ` Tomas Frydrych
2013-05-14 10:18                       ` Richard Purdie
2013-05-15 21:25                         ` Phil Blundell
2013-05-14 12:30                       ` libsoup missing DEPENDS Mike Looijmans
2013-05-14 12:36                         ` Burton, Ross

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=1368442968.6920.4.camel@phil-desktop.brightsign \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.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 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.