Comment 12 for bug 301189

Ok, this is going to be a bit of a mess. The problem is that, if I recall correctly, the update 3.1.1.0 -> 4.0.0.0 did work even on the packaged version. But maybe I'm mistaken.

Can anyone confirm that this actually happened:
- Installed 3.1.1.0 through package management.
- Updated to a newer version (e.g. 4.0.0.0) with the automatic updater.
- Verified that the update was successful and that azureus starts up as the new version.

If this is true, the azureus updater will be disabled by default but if the new version has already been downloaded we have to let the upgrade complete successfully. Otherwise some users will find themselves downgraded to 3.1.1.0 possibly losing settings and features. The downside of this solution is that if a users wants to stick with the ubuntu version (which should be the normal situation) he will have to manually delete his ~/.azureus directory.

To sum it up, we would:
- Turn the auto-update feature off by default.
- If a new jar has already been downloaded in the home directory, then use it.

I'm afraid the damage has been done to many home directories, which we cannot touch with package management. Blame debian for dropping the autoupdate-disable patch some time ago. :)

I think this is the way we should go, even if it doesn't really fit ubuntu's policy. I already implemented and tested this solution. If someone has suggestions, this is the time.