49 replies to this topic

[buyukbang]

@buyukbang: I have no confusion at all. I do believe it is your moral obligation to deliver source of your python plugin as a respect to the people that brought this project up to the point you had the option to add your code.
And this plugin of yours is nothing like "freeware application released as closed source project". Your work requires the existance of enigma2 and many more open source projects to have any kind of functionality.
Actually, this specific code of yours uses many GPL (and not LGPL) components (see your import list) so probably you are also violating GPL.

 

It seems as you just want a word play on words.

If so:

       Fix is written for VU+, VU+ uses Dvbapp2 not Enigma2 and all imports are OK for it, even enigma2. This way there will be no GPL violation

else:

       Not feeling guilty about that in anyway and my criteria is just this, not what others think.

 

BTW, for the freeware concept, your thesis are really weird and invalid. How do you call freeware applications with closed code that depends on Windows or Mac APIs. The word "freeware" is the commonly (minus u) accepted word for those

[betacentauri]

Hey guys, can you stop this useless(buyukbang don't have to publish his sources if he don't want it) discussion?

 

And buyukbang thanks for the plugin (even when I can't use it, because I have no solo2).

[buyukbang]

Hey guys, can you stop this useless(buyukbang don't have to publish his sources if he don't want it) discussion?

 

And buyukbang thanks for the plugin (even when I can't use it, because I have no solo2).

 

Thx for your understanding !

[Persian Prince]

actually i don't have time for argue

good luck killing each other

[malakudi]

Hey guys, can you stop this useless(buyukbang don't have to publish his sources if he don't want it) discussion?

 

And buyukbang thanks for the plugin (even when I can't use it, because I have no solo2).

 

He doesn't "have" to. I asked him to release them to avoid useless and potentialy risky scripts for postinst and postrm just to have binary for python 2.6 and 2.7 in his ipk. After all, the "plugin" doesn't do something that needs to be closed source. I also decompiled it before Persian Prince just to check what this fix is for - I want to know what is running in my box - of course it was not good to upload the decompiled version here. It's a simple fix/workaround in python for a bug in the drivers. Putting his blog url in the ipk filename also seemed bad to me.

 

I respect your work in enigma2. Personally, I would not put such an ipk in the 3rd-party plugins feed. If OpenPLI team thinks this is appropriate, then they can include it.

Edited by malakudi, 10 May 2013 - 15:23.

[Lost in Space]

dont't worry, I'm sure this will be killed with the VU drivers are buggy argument and stay a mess forever :-)

Edited by gutemine, 10 May 2013 - 16:10.

[buyukbang]

Hey guys, can you stop this useless(buyukbang don't have to publish his sources if he don't want it) discussion?

 

And buyukbang thanks for the plugin (even when I can't use it, because I have no solo2).

 

He doesn't "have" to. I asked him to release them to avoid useless and potentialy risky scripts for postinst and postrm just to have binary for python 2.6 and 2.7 in his ipk. After all, the "plugin" doesn't do something that needs to be closed source. I also decompiled it before Persian Prince just to check what this fix is for - I want to know what is running in my box - of course it was not good to upload the decompiled version here. It's a simple fix/workaround in python for a bug in the drivers. Putting his blog url in the ipk filename also seemed bad to me.

 

I respect your work in enigma2. Personally, I would not put such an ipk in the 3rd-party plugins feed. If OpenPLI team thinks this is appropriate, then they can include it.

 

My blog is just a personal blog, it does not include adds, donation buttons or any other commercial purposes. It is just a place to get together my personal freeware projects to share with people and it's not limited for E2. It's just a personal contact/information point and nothing more. So its difficult to understand objections on the URL.

 

In regards to the file name, I would only welcome PLi team if they need to rename the file to put it their servers. Their feeds have lots of closed source plugins, so I believe this will not be a problem.

Edited by buyukbang, 10 May 2013 - 18:05.

[korsan]

Very good job Buyukbang!

I assume this plugin is mainly meant for Dsmart CI module?

Does this plugin/fix also work on MaxDigital XP1000 E2 receiver, because with my Dsmart CI module the SD channels are ok, but I get artifacts on HD channels(The high bitate option is enabled).

[buyukbang]

Very good job Buyukbang!

I assume this plugin is mainly meant for Dsmart CI module?

Does this plugin/fix also work on MaxDigital XP1000 E2 receiver, because with my Dsmart CI module the SD channels are ok, but I get artifacts on HD channels(The high bitate option is enabled).

Hi korsan,

 

This fix is tested for Dsmart CI module but it should work for all CI modules requiring High Bit Rate. But I'm not sure why MaxDigital XP1000 E2 have issues with dsmart module. This plugin fixes a specifc VU+ Solo2 bug and if and only if MaxDigital have exactly same  bug, then it can be fixed.

[korsan]

Very good job Buyukbang!

I assume this plugin is mainly meant for Dsmart CI module?

Does this plugin/fix also work on MaxDigital XP1000 E2 receiver, because with my Dsmart CI module the SD channels are ok, but I get artifacts on HD channels(The high bitate option is enabled).

Hi korsan,

 

This fix is tested for Dsmart CI module but it should work for all CI modules requiring High Bit Rate. But I'm not sure why MaxDigital XP1000 E2 have issues with dsmart module. This plugin fixes a specifc VU+ Solo2 bug and if and only if MaxDigital have exactly same  bug, then it can be fixed.

Okay, I will test it soon on the XP1000..