Script to add & remove Plugins

[dRdoS7]

Hi,

Tiring of having to manually add (EPGRefresh, Foreca & Merlin Music Player), and remove various unwanted (you know which ones!!) plugins after each USB update. Some are even installed (updated though they've been removed?) in an online update.

I'd like to write a script that I can run once to do the above, it will have 2 effects: add & remove certain plugins, and save me accidentally removing the wrong one/s.

I think, like this:

Code: Select all

#!/bin/sh

opkg install enigma2-plugin-extensions-epgrefresh
opkg install enigma2-plugin-extensions-foreca
opkg install enigma2-plugin-extensions-merlinmusicplayer

opkg uninstall enigma2-plugin-extensions-hbbtv
opkg uninstall enigma2-plugin-extensions-inigmailreader
opkg uninstall enigma2-plugin-extensions-webcamviewer
opkg uninstall enigma2-plugin-extensions-youtube

opkg uninstall enigma2-plugin-systemplugins-icetv

How does that look?

EDIT: Not good: should be remove instead of uninstall!

Can/should I add some sort of error checking?

How do I make sure it has run correctly, can I get, and pause a screen output?

Thanks,

dRdoS7

[dRdoS7]

Hi,

An update after I tried the first, amended, version:

Code: Select all

#!/bin/sh

opkg install enigma2-plugin-extensions-epgrefresh
opkg install enigma2-plugin-extensions-foreca
opkg install enigma2-plugin-extensions-merlinmusicplayer

opkg remove --force-depends enigma2-plugin-extensions-hbbtv
opkg remove --force-depends enigma2-plugin-extensions-inigmailreader
opkg remove --force-depends enigma2-plugin-extensions-iniwebcamviewer

opkg remove --force-depends enigma2-plugin-systemplugins-icetv

I tried the last line, via telnet, and it worked. I'll try the script out when I do another USB FW update (on a non-vital T2 ).

dRdoS7

EDIT: Removed Youtube as it must be removed with Hbbtv (No package removed message).

[MrQuade]

I tried the last line, via telnet, and it worked. I'll try the script out when I do another USB FW update (on a non-vital T2 ).

You could also just stick the install and remove packages each into a single command if you like. Might be lightly less problematic if there is some unexpected error.

Code: Select all

#!/bin/sh

opkg install enigma2-plugin-extensions-epgrefresh enigma2-plugin-extensions-forca enigma2-plugin-extensions-merlinmusicplayer

opkg remove --force-depends enigma2-plugin-extensions-hbbtv enigma2-plugin-extensions-inigmailreader enigma2-plugin-extensions-webcamviewer enigma2-plugin-extensions-youtube enigma2-plugin-systemplugins-icetv
 

You could also copy the content of the "switch to beta feeds" script into this as well, though that is an unnecessary step with the current 16.1 beta series.

[prl]

...
Can/should I add some sort of error checking?

There aren't really any error conditions that you'd want to test for.

... How do I make sure it has run correctly, can I get, and pause a screen output?

There will be a fair bit of information printed by opkg anyway. You can feed the output of the script into a paginator, if you want to:

./plugin-installer 2>&1 | less

[dRdoS7]

Hi,

OK, updated the "spare" T2 to 20170222, after loading saved settings, installing OverlayHD, and several Reboots, I ran the script.

Strangely it wouldn't do the installs at first run, it removed a couple of plugins, and I noticed that I'd left "ini" off webcamviewer. Fixed that and ran it again, this time it did the installs, and removed the WCV. Actually, I had to run it 3 times, I can't remember exactly why, but finally, and after an couple of GUI Reboots, it was all clear.

I'll take more careful note next time.

I was getting this message, 3rd time, after it had run, installed the 3 plugins, and then I ran it again to uninstall the one that was incorrectly written:

Deprecated version constraint '>' was used with the same meaning as '>='. Use '> >' for LATER constraint.

A message about each plugin being up to date was also shown.

dRdoS7

[dRdoS7]

Hi,

Today I ran the script straight after an on line update, but before rebooting, and it worked fine. No problems encountered. Speeds things up a bit this way. I don't know why an on line update should install packages that I've previously removed.

dRdoS7

[Paul_oz53]

Love the script idea dRdoS7.

Can you post the refined version please? It will improve the upgrade process mightily if I can plagiarize your work.

I'll want to tailor it to the plugins I add and remove of course, reflecting the different ways we use our machines.

Like you, I also query the need to retain certain plugins like gmail and WebCams in the base build. Neither is of any real use nor being maintained from what I can see.

Many of us are IceTV addicts so we'll have to agree to disagree on that one.

Recently I killed both WebCams and Shoutcast. However, when I went to navigate across the vacant menu slot the machine crashed. Have you ever experienced a similar effect?

Thanks in advance,
Paul.

[dRdoS7]

Hi,

The second post has the script I'm using.

I had an idea that something should be left in sub-menu, and I leave Shoutcast, so I never had a crash. Only time was when I accidentally uninstalled the wrong plugin, which is why I wrote the script.

dRdoS7

[Paul_oz53]

Thanks,
I assume if I save the text in a .sh text file then I can run it as a script as I do for the beta feed script.
Paul

[dRdoS7]

Hi,

Thanks,
I assume if I save the text in a .sh text file then I can run it as a script as I do for the beta feed script.
Paul

Yes.

dRdoS7

[prl]

Thanks,
I assume if I save the text in a .sh text file then I can run it as a script as I do for the beta feed script.
Paul

It doesn't need to have a .sh extension (but it doesn't matter or do anything extra if it has the extension).

And with #!/bin/sh as the first line, if you enable its execute permission bits, you can just run it as a program, without explicitly running the shell (sh).

So if the script is in your current directory, you can just run:

./script_name

The same goes for the beta feed script.

[dRdoS7]

Hi,

Thanks,
I assume if I save the text in a .sh text file then I can run it as a script as I do for the beta feed script.
Paul

It doesn't need to have a .sh extension (but it doesn't matter or do anything extra if it has the extension).

And with #!/bin/sh as the first line, if you enable its execute permission bits, you can just run it as a program, without explicitly running the shell (sh).

So if the script is in your current directory, you can just run:

./script_name

The same goes for the beta feed script.

It makes it easier to open/edit in Windows if it has an extension. Otherwise I have to right-click and select an option, or if I left-click I have to select a program. It's not possible to set a default program without an extension.

I just used the .sh 'cause that was how the switch script was.

dRdoS7

[Paul_oz53]

Not being a Linux person I need to keep it simple too. But I appreciate the education!