OoZooN wrote:
Zitatis it a bug or a feature, that in the cvs version of moviecut the mcut binary is not shipped with the plugin? it's located in the package enigma2-plugins, but there is no packet depend from the moviecut ipk to enigma2-plugins
This is probably because this is my first attempt to upload things to enigma2-plugins, and I don't know of any other way of doing it.
But are you sure it is not included? Look again in Plugins/Extensions/MovieCut/bin/.
It all seems to be a mess. The practice seem to be to *not* include configuration files or binaries and such in the plugin ipk file, but rather collect them in the global enigma2-plugins ipk file. I wasn't aware of this practice when I wrote the control file, and even if I were I wouldn't know exactly how to describe the dependency to get the appropriate version of the enigma2-plugins package (i.e of the same date as the moviecut package). I assume that if I added the dependency, then everytime someone downloaded the moviecut ipk from the server they would automatically also receive the global enigma2-plugins package? But this also contains several configuration files for other plugins (not a good idea it seems), which means that those configuration files would be overwritten every time someone downloads my package!
So I wanted the binary included, and made an ugly fix to fool the automatic package builder to add it there (in addition to in the global package). But then it was not recognized as a binary file, so then I added an even uglier fix to make sure it was executable when the package is first loaded.
Well, thats the long story. I believe it works, but it certainly is not the right way of doing it. If anyone knows the right way, without the adverse effects mentioned above, I would be grateful to know it.
Best Regards
Anders Holst