35 replies to this topic

[Sjaaky]

We could open a github repo.

[hemertje]

read more about a possibility:

http://www.pli-image...078#post_216078

[Hump]

As of today, another Plugin (DreamExplorer) disappeared form the et feed. So far, so good. But, obviously the daily PLi Update also purges an existing plugin installation silently from the boxes, without the user knowledge or a warning. I'm sure that users are not very happy about this.

...but I know, the authors wishes have to be respected. I guess, the users wishes are not really important. At least users should be aware, that daily PLi software updates can and will remove any plugin (if originally installed from PLi feed) from their box, if so requested by the author.

Sorry, but this procedure really sucks.

[Jeroensky]

I think it's more useful to complain at the authors of the plugins who want to use weird licenses or agreements.

[Sjaaky]

I guess, the users wishes are not really important.

Well they are, but those of the author are more important.

[Hump]

I think it's more useful to complain at the authors of the plugins who want to use weird licenses or agreements.

I fully agree. But for PLi it should be sufficient to remove the Plugin from the feeds an not purge existing installations on boxes. That would show enough respect for the authors. Why mess up existing installations? I don't understand this at all!

[littlesat]

DreamExplorer is not compatible anymore for some reason. As it is a 3rd party plugin without having sources we cannot fix this. Please contact the auther of DreamExplorer. I suggest something goes wrong with the png improvements.

Please note that DreamExplorer is not removed at all yet...!!

[Jeroensky]

I think it's more useful to complain at the authors of the plugins who want to use weird licenses or agreements.

I fully agree. But for PLi it should be sufficient to remove the Plugin from the feeds an not purge existing installations on boxes. That would show enough respect for the authors. Why mess up existing installations? I don't understand this at all!

It's time for the Common Public E2 Plugin repository.
No bullshit, no horseshit, no cellularorganismshit, no extraterrestrialshit but just open plugins that can be used on any enigma2 device.

So who will start the time eating job with informing enigma2 authors about this Common Public Enigma2 OpenPlugin repository?

If it's online, then we can make in the plugin list, two lists, one for the open plugins, and one for the closed by manufactorer preference list (the fools list).

[Hump]

Ups, then I was wrong about the DreamExplorer Plugin. Sorry about this.

However, I still don't like the procedure for daily PLi Software Update deleting existing plugin installations on boxes, if so requested by authors.

[blzr]

calm down guys;-)
from your screens (in other section) it looks like it has something to do with yesterday's PicturePlayer plugin splitting, not with 'dmm wars' :-P
better ask @MiLo...

[ims]

DreamExplorer is not compatible anymore for some reason. As it is a 3rd party plugin without having sources we cannot fix this. Please contact the auther of DreamExplorer. I suggest something goes wrong with the png improvements.

Please note that DreamExplorer is not removed at all yet...!!

DreamExplorer cannot import Pic_Thumb and picshow from PicturePlayer plugin,py , because it was is moved to ui.py, thats all...

change line 44 in plugin.py in DreamExplorer to: from Plugins.Extensions.PicturePlayer.ui import Pic_Thumb, picshow

[MiLo]

As of today, another Plugin (DreamExplorer) disappeared form the et feed. So far, so good. But, obviously the daily PLi Update also purges an existing plugin installation silently from the boxes, without the user knowledge or a warning. I'm sure that users are not very happy about this.http://www.dict.cc/e...isappeared.html

If they are purged, that was never by design nor was it intentional. There is no mechanism at all to remove packages.
"DreamExplorer" is not in the PLi repository at all, so it's a 3rd party plugin.

(the removal of the Webinterface plugin was accidental: It wasn't actually removed, but replaced with a version that hardly contained any files. That has been fixed, but by then, it was already too late for most users.)

I can understand that you think you have the right to be pissed off, but that isn't justified because it is only based on the false assumption that we would actually want to remove packages from user's machines. I would like to know what the basis for your faulty assumption is. How did you come to your conclusion?

[MiLo]

DreamExplorer cannot import Pic_Thumb and picshow from PicturePlayer plugin,py , because it was is moved to ui.py, thats all...
change line 44 in plugin.py in DreamExplorer to: from Plugins.Extensions.PicturePlayer.ui import Pic_Thumb, picshow

Ah, if that's all, I can just add a few backward compatibility placeholders for them. There might be more plugins that attempt to do something similar.

[Hump]

If they are purged, that was never by design nor was it intentional. There is no mechanism at all to remove packages.
"DreamExplorer" is not in the PLi repository at all, so it's a 3rd party plugin.

I was wrong on this. I already aplogized. Sorry.

(the removal of the Webinterface plugin was accidental: It wasn't actually removed, but replaced with a version that hardly contained any files. That has been fixed, but by then, it was already too late for most users.)

In my opinion the existing plugin installations on users boxes should not be touched at all, if it would be a downgrade of the plugin. webif and webbouquet editor did not work at all, after the PLi Software update at that time. Removal of the Plugin on the feeds, should have been more then sufficient, to show respect for the author.

I can understand that you think you have the right to be pissed off, but that isn't justified because it is only based on the false assumption that we would actually want to remove packages from user's machines. I would like to know what the basis for your faulty assumption is. How did you come to your conclusion?

Well, if a working plugin installation gets replaced bei a than non-working (understand, that the old version was fixed after the fact) old version, than the original working version is removed - gone . Isn't it? ...wrong conclusion?

...btw, I'm not pissed, I'm just discussing this issue...and don't get me wrong, you guys are doing a great job for all of us. Thanks.

[MiLo]

For clarity:

This is the commit that removed the Webinterface. The effect should have been that the plugin simply wasn't being built any longer. The last version would remain in the feed, and even if not in the feed, that version would remain installed on any box.

http://openpli.git.s...8d17980943c3911

A few days later, pieterg figured out what went wrong and committed this fix:

http://openpli.git.s...a865ca209798ff7

Because the Webinterface directory still existed after the build, the packager picked it up as being the new version, thereby destroying the previous one.

[Hump]

@Milo,

thanks for the clarifacation. Shit happens sometimes. That isn't problem at all!