All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/5] Enable VPN support in ConnMan
Date: Mon, 13 May 2013 09:33:25 +0100	[thread overview]
Message-ID: <11599561.3zUhJSzPUZ@helios> (raw)
In-Reply-To: <51909DB8.3060407@linux.intel.com>

On Monday 13 May 2013 11:00:56 Saul Wold wrote:
> On 05/12/2013 10:55 PM, Paul Eggleton wrote:
> > On Sunday 12 May 2013 19:54:50 Phil Blundell wrote:
> >> On Sun, 2013-05-12 at 08:40 -0700, Saul Wold wrote:
> >>> On 05/12/2013 06:27 AM, Otavio Salvador wrote:
> >>>> I think so, it'd be good to have it in oe-core and allow use of vpn :)
> >>> 
> >>> I would like to see what the full dependency set looks like for these,
> >>> clearly there is the vpnc, openvpn, l2tp and pptp recipes, but what else
> >>> and what licenses are they under.
> >> 
> >> I don't think we necessarily want openvpn, l2tpd and suchlike in
> >> oe-core.  None of those things seem very "core" to me (in an embedded
> >> context) and testing them seems like it would be a bit of a challenge.
> > 
> > I agree, these don't belong in OE-Core. We already have them in meta-
> > networking.
> 
> This is what I get for replying to an email while traveling overseas and
> not being 100% clear about my points.
> 
> I was more interested in the dependencies then actually thinking about
> including them in OE-Core,that was not my intent.
> 
> This would would allow us to better understand if those recipes not in
> meta-networking could be moved from meta-oe to meta-networking.
> Currently, I think vpnc and pptp are in meta-networking, not the other 2.

They are all in meta-networking (xl2tpd, pptp-linux and vpnc have always been 
there, openvpn got moved in mid-April).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2013-05-13  8:51 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 [this message]
2013-05-13  8:44                 ` Saul Wold
2013-05-13 11:02             ` Phil Blundell
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=11599561.3zUhJSzPUZ@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@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.