History Zap Selector by ©Dorik1972

There are 353 replies in this Thread which was already clicked 53,977 times. The last Post () by ian1095.

    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

    Hi. I have error on last version.

    root@dm920:~# /tmp/*deb

    /tmp/enigma2-plugin-extensions-historyzap_1.0.44_all.deb: line 1: syntax error near unexpected token `newline'

    /tmp/enigma2-plugin-extensions-historyzap_1.0.44_all.deb: line 1: `!<arch>'

    Sorry my mistake.


    root@dm920:~# apt install /tmp/*.deb

    Reading package lists... Done

    Building dependency tree

    Reading state information... Done

    E: Unable to locate package /tmp


    If i try install this package from box menu I can see package. Install is proceed but plugin is not install.

    Quote from pepsik

    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:

    Quote

    792 unlink("/tmp") = 0

    Edited once, last by birdman2 ().

    Quote from birdman2

    There's a bug, at least in the ipk versions here.

    Because you now install the compiled __init_.pyc and plugin.pyc via /tmp

    In the installation scripts, I use this "trick":

    Code
    PluginName="Historyzap"
/tmp/$PluginName/****

    i.e., during installation, the files will be extracted to /tmp/Historyzap/ .....Accordingly, when uninstalling the plugin, the /tmp folder will not be affected ... Either I misunderstood you

    Quote from birdman2

    From an strace of the remove:

    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

    if you like it you can make donations

    Quote from pepsik

    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?

    Quote from birdman2

    There is no need to use ./tmp

    It is my decision to do so ... Earlier, I did as you wrote, copying to the plugins folder, but there were certain reasons why I stopped doing that and did it the way I did it. Even in the variant you describe, you will still have to “wipe tails” in *.list files to avoid error messages when deleting or updating the plugin


    Quote from birdman2

    because you install to /tmp opkg remember

    That's not me doing that, that's how “opkg” command works =) ... Simplified - it just unpacks the contents of the package by “memorizing” the files and paths in it in a specially designated “place”

    Quote from birdman2

    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"


    Quote from birdman2

    Even simpler would be to jiust use

    It's not too difficult for me to add a few lines to a bash script =) to do exactly what I have in mind ...

    if you like it you can make donations

    Quote from pepsik
    Quote from birdman2

    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?

    Quote from birdman2

    The original was distributed under the GPL

    What do you consider original? Read the topic carefully. I have already written that there are many such plugins, but I wrote mine in the form and in the way I considered necessary... Quite a large number of the first versions of this plugin are in the public domain ... You can familiarize yourself and compare with what you consider some of the originals =) ...


    Quote from birdman2

    So, please, where is the source?

    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 ... Before that, look, everything is open there

    if you like it you can make donations

    Quote from pepsik

    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.

    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.

    Edited once, last by birdman2 ().

    Quote from birdman2

    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.

    Whether the code will be closed or open is not for you to decide =) ... . . . Trust me. You can only use this plugin or not :) You have a choice of other plugins with similar functionality, as you wrote above, “original”. Use them. Don't torture yourself. Thanks for understanding


    Quote from birdman2

    I could investigate,

    Thanks, but my level of python proficiency is more than enough to understand my code and make changes to it if you provide me with an error log

    if you like it you can make donations

Your hub for Enigma2 DreamOS plugins

Find downloads, installation guides, and support for Dreambox devices and DreamOS images. Official forum for Enigma2 DreamOS plugins. Download the best extensions and get setup help for your Dreambox system.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login