Re: [meta-oe][meta-networking][PATCH V2 3/3] ntp: Clean up recipes

[Paul Eggleton <paul.eggleton@linux.intel.com>]

On Friday 02 November 2012 10:02:23 Joe MacDonald wrote:
> On 12.11.02 (Fri 13:38) Paul Eggleton wrote:
> > I have to say I think that these days this could be better implemented
> > as one ntp recipe with a PACKAGECONFIG that you can use to enable
> > OpenSSL support if desired. (At the time the ntp/ntp-ssl split was
> > done, PACKAGECONFIG did not exist). Then it becomes a distro-level
> > choice as to whether this is enabled as I believe was originally
> > intended.
> 
> I'm also perfectly fine with that.  Question, though.  Do you mean that
> the presence of OpenSSL in the distro would then mean you get ntp-ssl
> all the time?  That would be fine for me, but I wonder if anyone else
> might want OpenSSL on their system but a non-ssl-enabled ntp?  Probably
> a silly case to be thinking about anyway.

The idea with PACKAGECONFIG is it allows per-recipe control over this kind of 
thing. The default would be for OpenSSL support to be disabled, but it could 
be enabled with a bbappend containing PACKAGECONFIG += "openssl"; 
alternatively you could do PACKAGECONFIG_append_pn-ntp = " openssl" in the 
distro .conf file or even local.conf.

I'll send a patch.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre