SageTV V7 plugin installation in linux

[michaeldjcox]

If your plugin includes some executable components.

Would I be right in assuming that you need to get your plugin implementation to chmod all those to be executable when the plugin is enabled?

For some reason I was under the mistaken impression that if I chmod the shell scripts and exes to be executable, zipped it up and published to the world...

...that when SageTV unzipped the plugin on install that the executability of files would be preserved.

Michael

[tmiranda]

Michael,

I'm not a linux expert by any stretch of the imagination. My experience is the same as yours, you need to use chmod to make the programs executable.

Tom

[stuckless]

Originally Posted by michaeldjcox

If your plugin includes some executable components.

Would I be right in assuming that you need to get your plugin implementation to chmod all those to be executable when the plugin is enabled?

For some reason I was under the mistaken impression that if I chmod the shell scripts and exes to be executable, zipped it up and published to the world...

...that when SageTV unzipped the plugin on install that the executability of files would be preserved.

The issue, is that .zip files do not maintain file attributes, which is why in unix systems, people never use zip, but rather tar (and then gzip).

So, your .zip files will never transfer a unix executable (ie, a file with the execute flag enabled). I don't know what your executable is, but I'd suggest (at least for linux) you simply have the end users install it separately. For one thing, if you ship a linux binary, you'll need to worry about 32bit/64bit and you'll also have to ensure that it's statically linked, etc. I would also think that most linux users (if not all) should know how to install a particular dependency using their respective package managers, etc.

If you do need to deploy a unix exectuable, then you'll need to chmod the file yourself form the Plugin class.

[michaeldjcox]

Originally Posted by stuckless

The issue, is that .zip files do not maintain file attributes, which is why in unix systems, people never use zip, but rather tar (and then gzip).

So, your .zip files will never transfer a unix executable (ie, a file with the execute flag enabled). I don't know what your executable is, but I'd suggest (at least for linux) you simply have the end users install it separately. For one thing, if you ship a linux binary, you'll need to worry about 32bit/64bit and you'll also have to ensure that it's statically linked, etc. I would also think that most linux users (if not all) should know how to install a particular dependency using their respective package managers, etc.

If you do need to deploy a unix exectuable, then you'll need to chmod the file yourself form the Plugin class.

I have a number of executables depending on platform and a shell script related to starting and stopping something as a service on many different platforms if not every significant platform.

Thanks for the informed description of why it don't work :-)

I shall chmod from my plugin class.

Many thanks,

Michael