The idea I explained in IRC: Instead of applying the fedora patchset, which is hard to maintain, one could try to create patches that simply grey out/disable some options from the mainmenu and configuration tab. That may be easier to maintain I guess/hope. These options would be: - restarter - azureus updater Any other options?
(In reply to comment #0) Just for the record (dunno if it was said on IRC but should be here too anyway) I want to know this: > These options would be: > - restarter Is it harmful, breaking with our startup script or why remove that? > - azureus updater I think it also updates user-installed plugins so that would be removing also wanted functionality... Also updater can be started automatically on startup, so greying out the menu does not solve it. Ideally azureus should distinguish between system (core, swt, ...?) and user plugins and let us allow only user plugins update.
The restarter just did not do what it should. does it behave now? Just as i wrote 'azureus updater' not 'plugin updater'. ;)
As well for any callback handling that needs to be disabled. Just forgot to mention it properly. But has to be done anyway, so. ;)
Ok, restarter is fixed: bug 219177 So, only azureus updater, which wants to update azureus core, may still be disabled.
*** Bug 200683 has been marked as a duplicate of this bug. ***
Right so with restarter out of the way in 4.0.0.2 the problem remains updater. From what I can see there is only one updater that updates everything - core components, shared plugins (newly introduced) and user-installed plugins. Because of the user plugins we should not disable updater entirely, but modify it to not notify user of and update core and shared stuff, leaving the user plugin update working. Now it notifies and tries to update everything which fails and is annoying. For even better user experience we could also consider disabling - warning that shared plugin directory is not writable (now you have to check that you don't want to see the warning again) - during plugin install, the selection between shared and user directory (since only user makes sense) Anything else? Patches? :)
Hmm, I wonder, the patch from [0] seems to disable only core updater. azureus updater and plugin updater plugins are still there. :) [0] http://lists.debian.org/debian-policy/2007/01/msg00047.html
Created attachment 195655 [details, diff] disable core updater up to date patch for vuze-4.2.0.2
(In reply to comment #8) > Created an attachment (id=195655) [edit] > disable core updater > > up to date patch for vuze-4.2.0.2 Applied in 4.2.0.2-r1, thanks! Guess that leaves a check for swt and shared plugins.
(In reply to comment #9) > Applied in 4.2.0.2-r1, thanks! Guess that leaves a check for swt and shared > plugins. Added these in 4.4.0.0. Yet I now see that something could still be improved: (In reply to comment #6) > For even better user experience we could also consider disabling > - warning that shared plugin directory is not writable (now you have to check > that you don't want to see the warning again) > - during plugin install, the selection between shared and user directory (since > only user makes sense)
Reopen if you're still planning to work on this.
