On Sun, 2013-05-12 at 08:40 -0700, Saul Wold wrote: > On 05/12/2013 06:27 AM, Otavio Salvador wrote: > > On Sat, May 11, 2013 at 10:59 AM, Philip Balister <phi...@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.
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. Equally, we certainly don't want to have dependencies in oe-core pointing to packages in meta-oe or any other layer, since this would make it impossible to test oe-core in isolation. So I would be inclined to say that the right way to deal with this is for those connman bits to go in a .bbappend which lives in the same layer as the recipes in question. p. _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
