Make a separate upgrade rpm/deb and make it a dependency on upgrading
existing install.
During it's install stop output text to screen to look at the users
guide as well as a list of the detected databases and ask for which ones
to upgrade and the then prompt for the dbuser and pass required. The
users guide would be referred for in depth analysis of the procedure.
If they want to study the users guide they can opt out of the upgrade
right there. Simple user friendly and problem prevention way to do
upgrades.
signaturehtmlsteve *Steve Boley*
<http://www.nams.net>
On 7/30/2015 8:09 AM, Sven Schwedas wrote:
On 2015-07-30 15:05, Chris Coleman wrote:
On 7/30/2015 8:57 AM, Christian Mack wrote:
Hello
Am 30.07.2015 um 14:24 schrieb Márcio Merlone:
On 24-07-2015 08:07, Steve Ankeny wrote:
The only issues I remember with the running of the script were --
(1) users fail to run it
(2) or, they run the wrong script
Instructions are *always* at the back pages of the Installation
Guide --
http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf (pg 58)
Since I run Ubuntu, I assume the install/upgrade procedure from apt
already does that, is this correct?
No!
You have to do that manually.
Kind regards,
Christian Mack
I nominate adding the database schema upgrade script to the deb and rpm
install/upgrade scripts. It would need to detect the current db schema
version and apply the appropriate db updates. Which it surely does
already...
That automation alone would probably reduce friction by 5%.
Assuming it doesn't have any bugs and blows up your whole database. You
should read the notes anyway, because schema migrations aren't the only
changes between versions.
--
[email protected]
https://inverse.ca/sogo/lists
