From: Saul Wold <sgw@linux.intel.com>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/5] Enable VPN support in ConnMan
Date: Sun, 12 May 2013 08:40:41 -0700 [thread overview]
Message-ID: <518FB7F9.2020102@linux.intel.com> (raw)
In-Reply-To: <CAP9ODKoB_KzEPvRwDkZxLgq4d5A5DiPZ+gfko5XgF3qp9fP_xQ@mail.gmail.com>
On 05/12/2013 06:27 AM, Otavio Salvador wrote:
> On Sat, May 11, 2013 at 10:59 AM, Philip Balister <philip@balister.org> wrote:
>> On 05/10/2013 06:22 PM, Saul Wold wrote:
>>> On 05/10/2013 05:33 AM, Jukka Rissanen wrote:
>>>> The VPN support is activated if DISTRO_FEATURES contains
>>>> vpn string.
>>>>
>>>
>>> This also create a dependency on the meta-openembedded layer, I am not
>>> sure we want to do that.
>>
>> If the default setting does not add the dependency it should be OK? What
>> packages in meta-oe are needed? Does this suggest they should move to
>> oe-core?
>
> 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.
Sau!
> --
> Otavio Salvador O.S. Systems
> E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
> Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
>
>
next prev parent reply other threads:[~2013-05-12 15:59 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 [this message]
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
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=518FB7F9.2020102@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=jukka.rissanen@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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