[Openembedded-architecture] LSB is dead; when shall we drop it?

Otavio Salvador otavio.salvador at ossystems.com.br
Fri Apr 7 13:29:34 UTC 2017


On Fri, Apr 7, 2017 at 10:18 AM, Alexander Kanavin <
alexander.kanavin at linux.intel.com> wrote:

> On 04/07/2017 04:07 PM, Mark Hatle wrote:
>
> (Really making sure this keeps working should not be more then a day or so
>> work
>> over the course of every stable release.  If it is, we need to understand
>> what
>> is causing this work.)
>>
>
> I trust you do understand the concept of "bit rot" and the maintenance
> overhead it's causing? Here's a specific example: this week day I was
> introducing openssl 1.1 into oe-core, and checking a dozen recipes that are
> not compatible with it by hand to see what, if anything, they are doing
> about it.
>
> Qt4 is one such component, and it's pretty clear it will never be
> compatible with openssl 1.1. So I ended up disabling ssl support in Qt4 -
> which was thankfully not difficult to do, but is a regression in Qt4 API we
> provide. I expect Qt4 will continue to be a source of similar issues in the
> future as we move on with the times in oe-core, and at some point there
> will be an issue that is not easy to resolve without disabling Qt4
> altogether.
>
> Another LSB-mandated component is mailx, which is also dead upstream, and
> requires openssl 1.0. When openssl 1.0 becomes unsupported at the end of
> 2019, what are we supposed to do? Not clear to me now.


The main question here is if we are going to keep OpenSSL 1.0 and 1.1 in
parallel inside OE-Core or not. For Pyro I think we should stay on 1.0 or
have 1.1 as an opt-in option, but for 2.4 I would say to drop 1.0 if
possible and move 1.0 to a layer ... potentially, lsb support could be
moved to a layer as we did with gplv2 and qt4.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-architecture/attachments/20170407/4079da64/attachment-0002.html>


More information about the Openembedded-architecture mailing list