I made a change to my plugin (2 lines) to play around with the nonsense of overriding the EventViewBase class in the EPG-Translator plugin code.
It's not an override (very specifically not an override). It intercepts it, calls the original (whatever was there at initialization time) then adds what EPGTranslator needs. You should have been doing the same from the start.
Glad you've finally found your bug that was affecting other code even without yours being mentioned in the crash log.
The code is yours. It's up to you. Those who need it to work can fix one line as I wrote above, and.... it will work.
Pity I can't do that to yours and fix the real problem, rather then the symptom.
Somewhere above in any of the crash logs is there even a line or letter mentioning my code?
If you think that is relevant then you clearly have no idea about how enigma2 works. Or can't be bothered to think.
Let's start with the fact that the crash does not occur in my code .
But it is a caused by your code as you've done something that means you've gone through the set-up code for EPGTranslator, but then wiped out part of the result of doing so and hence end up in part of my code without going through the associated initializing code despite these two thing being set-up at the same time.
As I've noted, were your code available I might be able to fix it, but since it isn't I'll have to let you stay with your bugged code. I see no reason to add unnecessary code to EPGTranslator to handle someone else's undisclosed oddities.
This is an ongoing conflict between Epgtranslator and hzs that was reported a long time ago. You need to choose one of them to use. Once you install hzs, you will not be able to use Epgtranslator. I believe both plugins attempt to perform the same action, which is why the crashes occur.
No. The crash occurs because HZS doesn't run the intercepted call (EventViewBase.__init__())correctly.
If it did there would be no crash.
The result might not be exactly what is wanted, but there doesn't need to be a crash.
Of course, since the HZS code is not available we're not able to check this and fix it.
Whether the code will be closed or open is not for you to decide =) ..
If it started out as GPL code it's not for you to decide, no matter how much you've added to it. That's the relevant part here.
And this plugin has a bug in that it intercepts entrypoints in a way that can make enigma2 crash.
If you made this GPL code available I could investigate, but since you are withholding it I'll just report your code is bugged.
Since a certain version, when I added advanced functionality (search by channel name, auto-translate to any selected language, etc.) the code stopped being available.
If it was under the GPL (and the presence of GPLv3 in the code indicates that it was) then any derivatives (such as continued development of it) must also be under the GPL.
This is distributed under GPLv3, so the source has to be made available anyway.
Ignore it =) It's a vestige of the past, I'll remove that too, and change its status to "proprietary software"
You can't do that!
The original was distributed under the GPL and so that holds for anything derived from it that continues to be distributed.
This cannot legally be proprietary software.
So, please, where is the source?
i.e., you want to say that when you remove the plugin, the error in the log described above occurs. Okay. I agree that this is possible. I will add syntax analysis of the list-file and clean it up in postinst from “unnecessary” references to /tmp
Yes. because you install to /tmp opkg remembers that and when you remove (or upgrade) a package it deletes the imnstalled files which are no longer there.
There is no need to use ./tmp at all. Just install all of these files to the plugin location tagged with their version then rename the ones you want and delete all of the others.
Even simpler would be to jiust use the *.py files for __init__.py and plugin.py.
This is distributed under GPLv3, so the source has to be made available anyway.
So where is the source for these two files?
UPDATE
1.0.44
1) Code fixes to support the latest OpenBH images, OpenPli Scarthgap, etc.
2) Slightly modified installation scripts for compatibility with Python3-based images that lack the "python" symlink
There's a bug, at least in the ipk versions here.
Because you now install the compiled __init_.pyc and plugin.pyc via /tmp then /tmp gets added to the /var/lib/opkg/info/enigma2-plugin-extensions-historyzap.list file. Consequently it gets removed if you remove the package.
From an strace of the remove:
Quote792 unlink("/tmp") = 0
