←  [EN] Third-Party Development

Forums

»

devel-next: hardknott or honister

A.A.'s Photo A.A. 26 Aug 2021

Hi,

 

just to start a discussion about the issues with the migration to recent OE:

 

hardknott

+ we can keep samba with a minimal patch to use python2

+ we can keep the old _override operator

- kodi is stuck to 18.x

 

honister

- newer samba: we must upgrade to python3

- tune-files have moved

- we must convert the override operator

 

As for the necessaries BSP changes, it could be done in one or two steps (overrides now, tune-files later).

 

Finally I see OE-A is using python3 for enigma images.

What is the status here?

A.A.
 

 

 

Quote

WanWizard's Photo WanWizard 26 Aug 2021

In general the response has been for many years "we don't like big changes because something might break" (mainly referring to third-party code).

 

Which has blocked many suggestions for improvements. Now reality is catching up with us...

 

My 2cts:

 

Base OpenPLi 9 on hardknott, stiill using Py2, and go for whatever is stable then for OpenPLi 10. Simply because of the amount of work and timeframe.

 

Then create a project to upgrade Enigma, not only simply the Py2 to Py3 change, but also deal with all the old rot in the codebase (like a network browser that only supports NetBIOS, network config that doesn't support IPv6, the complete spaghetti in menu options and configuration, etc). Run it like a project, with todo's, issue tracker, etc.

 

And aim to release that with OpenPLi 10.

Quote