Jump to content


Photo

devel-next: hardknott or honister


  • Please log in to reply
1 reply to this topic

#1 A.A.

  • Senior Member
  • 391 posts

+8
Neutral

Posted 26 August 2021 - 10:18

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.
 

 

 



Re: devel-next: hardknott or honister #2 WanWizard

  • PLi® Core member
  • 70,849 posts

+1,832
Excellent

Posted 26 August 2021 - 12:30

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.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.



1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users