Re: [oe] [meta-networking][PATCH] strongswan: Split plugins

2017-04-27 Thread David Vincent
Sorry for the late reply, I've seen the patch has been merged into master-next but I let this thread unanswered. Here are some thoughts to explain it. On mercredi 26 avril 2017 16:57:29 CEST Joe MacDonald wrote: > [Re: [oe] [meta-networking][PATCH] strongswan: Split plugins] On 17.04.20 (Thu

Re: [oe] [meta-networking][PATCH] strongswan: Split plugins

2017-04-26 Thread Joe MacDonald
[Re: [oe] [meta-networking][PATCH] strongswan: Split plugins] On 17.04.20 (Thu 16:36) Martin Jansa wrote: > I think currently the preferred way is only one -dev/-dbg/-staticdev > package per recipe. > > Why not set RDEPENDS_${PN} based on plugins packaged in first > do_spli

Re: [oe] [meta-networking][PATCH] strongswan: Split plugins

2017-04-20 Thread Martin Jansa
I think currently the preferred way is only one -dev/-dbg/-staticdev package per recipe. Why not set RDEPENDS_${PN} based on plugins packaged in first do_split_packages call? Just my 2c - I'm not using strongswan and Joe has last word for meta-networking. On Thu, Apr 20, 2017 at 3:57 PM, David

[oe] [meta-networking][PATCH] strongswan: Split plugins

2017-04-20 Thread David Vincent
strongSwan offers a plugin mechanism therefore it should not be mandatory to install all of them when installing the package. Each plugin is now a self-contained package with the library and its configuration. To remain compatible with the current configuration, a default set of plugins has been