Plugin manager auto backup old plg on update

[Squid]

I just tried and confirmed the plugin manager won't install a previous plg version currently.

 

Also if the plugin is installed with a versioned txz then using upgradepkg --install-new will remove the existing plugin files and install the package. Doesn't matter if version is old or new it will remove existing files.

From the CA release notes:

Note that no-one (including myself) is ever going to implement a "rollback" button to handle a rollback automatically, as the time and energy required for this isn't worth it for how many times it may get used.  Rolling back will remain a manual operation of copying the backup to /boot/config/plugins and rebooting the server.

[dmacias]

I just tried and confirmed the plugin manager won't install a previous plg version currently.

 

Also if the plugin is installed with a versioned txz then using upgradepkg --install-new will remove the existing plugin files and install the package. Doesn't matter if version is old or new it will remove existing files.

From the CA release notes:

Note that no-one (including myself) is ever going to implement a "rollback" button to handle a rollback automatically, as the time and energy required for this isn't worth it for how many times it may get used.  Rolling back will remain a manual operation of copying the backup to /boot/config/plugins and rebooting the server.

I agree but right now the plugin manager only saves a backup of removed plugins to /boot/config/plugins-removed. It could be easily modified to save a copy of upgraded plugins to lets say /boot/config/plugins-old and allow installation of a previous version. Any of my plugins could be rolled back as they are written now without any effort from me if the plugin manager allowed it.

[Squid]

I just tried and confirmed the plugin manager won't install a previous plg version currently.

 

Also if the plugin is installed with a versioned txz then using upgradepkg --install-new will remove the existing plugin files and install the package. Doesn't matter if version is old or new it will remove existing files.

From the CA release notes:

Note that no-one (including myself) is ever going to implement a "rollback" button to handle a rollback automatically, as the time and energy required for this isn't worth it for how many times it may get used.  Rolling back will remain a manual operation of copying the backup to /boot/config/plugins and rebooting the server.

I agree but right now the plugin manager only saves a backup of removed plugins to /boot/config/plugins-removed. It could be easily modified to save a copy of upgraded plugins to lets say /boot/config/plugins-old and allow installation of a previous version. Any of my plugins could be rolled back as they are written now without any effort from me if the plugin manager allowed it.

And that's what my PR to LT does (just organizes it by date however)

[Riot]

Wow. Talk about traction. I got the big dogs in here

 

Just want to say thanks to all of you for discussing and looking into this.

[Squid]

Wow. Talk about traction. I got the big dogs in here

 

Just want to say thanks to all of you for discussing and looking into this.

http://www.dictionary.com/browse/cause-celebre  (or maybe we all had nothing better to do    )